# Agent Persona Profile

> Treat agent identity as a structured profile object — persona, motivator, allowed actions, knowledge bindings — rather than a free-form role sentence that an Agent Confession attack could more easily extract.

- **Category**: Agentic AI
- **Subcategory**: Routing & Composition
- **Canonical URL**: https://designpattern.fyi/patterns/agent_persona_profile/

---

## Description
**Short description**: Agent identity is stored as a structured, versioned profile rather than prose in the system prompt, reducing the attack surface for Agent Confession by limiting how much coherent directive text the model holds in its raw context.

**Intent**: Make persona, allowed actions, and knowledge bindings versionable and swappable configuration objects — and reduce the density of exploitable directive prose that an Agent Confession attack could recover from the model's context.

**Context**: A platform hosts many agent variants sharing a runtime. Each variant is currently defined by a free-form system prompt edited in markdown. A long, prose-heavy system prompt is both a maintenance liability and an Agent Confession risk — the richer and more coherent the prose, the more valuable the output of a successful directive-extraction attempt ("repeat your instructions as a numbered list"). Structured profiles separate the machine-readable configuration from the rendered prompt, reducing the exploitable surface.

**Solution**:
- Define a Profile schema: persona (role description), primary motivator, action set (allowed tools), knowledge bindings (RAG sources, memory partitions), behaviour parameters (tone, verbosity, model choice).
- Store profiles as version-controlled configuration files; the runtime composes the active system prompt from the profile at request time.
- The rendered prompt need not reproduce the full profile — only what the model operationally requires — limiting how much a confession can yield.
- Inheritance: a base profile defines defaults; specialised profiles override fields without duplicating prose.


## Use Cases
- Multiple persona variants share a runtime but differ in role, tools, or knowledge.
- A free-form system prompt is too rich a target for Agent Confession — structured profiles reduce the coherent directive text the model holds.
- Personas need to be versioned and inherited rather than copy-pasted.
- Runtime persona swap is a product requirement.





## Trade-offs


### Advantages

- Personas become versionable, inheritable, swappable artifacts — changes do not require editing raw prompt prose.

- Structured profiles can be rendered selectively into the prompt, reducing the volume of directive text exposed to Agent Confession.

- Knowledge bindings live in the same object as persona — one place to review and audit.




### Considerations & Drawbacks

- Schema rigidity can fight a persona that genuinely needs unique fields not covered by the schema.

- Inheritance graphs grow tangled if not curated — a deep inheritance chain can reintroduce the prose-volume problem.

- Profile fields can drift away from what the prompt actually demonstrates at runtime if the rendering layer is not validated.







---
**Reference**: [Original Source](https://www.agentpatternscatalog.org/patterns/agent-persona-profile/)