A command that creates a new persona definition for the awesome-mcp-personas registry. A persona is a reusable description of an AI assistant's role, audience, work area, and required tools.

Use it to define a persona's purpose, target users, work domain, and essential tools through a structured question-and-answer process.

It turns the requirements for a persona into the configuration files expected by the registry, reducing the chance of missing important details or using the wrong format.

new-persona — Command for Claude Code by toolprint

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/toolprint/awesome-mcp-personas

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/toolprint/awesome-mcp-personas/new-persona/github.svg)](https://agentmods.dev/commands/toolprint/awesome-mcp-personas/new-persona)

Your own site

<a href="https://agentmods.dev/commands/toolprint/awesome-mcp-personas/new-persona"><img src="https://agentmods.dev/badge/commands/toolprint/awesome-mcp-personas/new-persona/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/toolprint/awesome-mcp-personas/new-persona"><img src="https://agentmods.dev/badge/commands/toolprint/awesome-mcp-personas/new-persona.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,120 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01120
Opus 5.5	$0.00000	$0.00448
Sonnet 5.5	$0.00000	$0.00224
Haiku 4.5	$0.00000	$0.00112

Measured 2mo ago against content hash b6d44458b076, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

new-persona scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/proj/new-persona.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/new-persona

Generate a new persona definition for the awesome-mcp-personas registry.

Purpose

This command helps users create a new persona by walking through a structured Q&A process to gather requirements and generate the necessary configuration files following the project schemas.

Process

1. Initial Questions

Ask the user these questions to understand their persona requirements:

Q1: Basic Information

What is the name of your persona? (lowercase, hyphen-delimited, e.g., "data-scientist", "frontend-developer")
Provide a brief description of this persona's purpose (10-500 characters)
Who is the target audience for this persona?

Q2: Work Domain

What type of work will this persona primarily do? (Choose one or more)
- Software Development
- Data Analysis
- DevOps/Infrastructure
- Content Creation
- Security/Compliance
- Research
- Other (specify)

Q3: Core Tools

What are the essential tools/capabilities this persona needs? (List key functionalities)
- Version control (git)
- File system operations
- Language-specific tools (npm, pip, cargo, etc.)
- Testing frameworks
- Database access
- API interactions
- Cloud services
- Other (specify)

Q4: MCP Servers

Do you have specific MCP servers in mind? (If yes, list them)
Should I research and suggest appropriate MCP servers based on your requirements? (Uses @mcp-researcher agent)

Q5: Toolsets Organization

Do you want multiple toolsets for different workflows? (e.g., "development", "testing", "deployment")
If yes, describe the different workflows/contexts

Q6: Transport Preferences

What type of MCP server connections do you prefer?
- stdio (standard I/O) - Default, most common
- http (HTTP endpoints)
- sse (Server-Sent Events)
- Mixed (different servers use different transports)

2. Initial README Generation

Based on user requirements, create a comprehensive README.md as the foundation:

Step 2a: Generate Initial README

Create directory and generate README.md using /schema/README.template.md:

personas/[persona-name]/
└── README.md (with persona requirements and use cases)

Read the full file on GitHub · 133 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 133 lines · 0 tokens per session scan A b6d44458b076

Subscribe to this mod's changes

new-persona is a command published in the GitHub repository toolprint/awesome-mcp-personas (39 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,120 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agents Claude Code agents codex cursor mcp modelcontextprotocol

new-persona next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
new-personatoolprint/awesome-mcp-personas	Command	39	1y ago	MIT	A	0	Claude Code
rfcluca-mastrostefano/agent-native-setup	Command	7	yesterday	MIT	A	12	Claude Code
t800-startKhar-AG/t-800-agent	Command	8	2mo ago	MIT	A	0	Claude Code
pn-audit-dataperniemann/pnCore	Command	0	5d ago	MIT	A	42	Claude Code, Cursor
pn-delightperniemann/pnCore	Command	0	5d ago	MIT	A	30	Claude Code, Cursor
t800-updateKhar-AG/t-800-agent	Command	8	2mo ago	MIT	A	0	Claude Code
t800-doctorKhar-AG/t-800-agent	Command	8	2mo ago	MIT	A	0	Claude Code