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.
git clone --depth 1 https://github.com/toolprint/awesome-mcp-personasWrote 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.
[](https://agentmods.dev/commands/toolprint/awesome-mcp-personas/new-persona)<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.
<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>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 | $0.00000 | $0.00560 |
| Sonnet 5 | $0.00000 | $0.00224 |
| Haiku 4.5 | $0.00000 | $0.00112 |
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 11d 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.
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)
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.
- 11d ago First seen · 133 lines · 0 tokens per session scan A b6d44458b076
new-persona is a command published in the GitHub repository toolprint/awesome-mcp-personas (39 stars, last pushed 12mo 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.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
api-mock
You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing.
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
data-driven-feature
Build features guided by data insights, A/B testing, and continuous measurement.