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/sync-personas)<a href="https://agentmods.dev/commands/toolprint/awesome-mcp-personas/sync-personas"><img src="https://agentmods.dev/badge/commands/toolprint/awesome-mcp-personas/sync-personas/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/sync-personas"><img src="https://agentmods.dev/badge/commands/toolprint/awesome-mcp-personas/sync-personas.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.00488 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
sync-personas 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 13d 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.
What it actually says
/sync-personas
Scans the personas directory and automatically updates the top-level README.md with any new or missing personas, following all established guidelines for categorization, emoji labeling, and table formatting.
Usage
/sync-personas
What it does
- Scans personas directory - Discovers all valid persona configurations
- Validates persona structure - Ensures required files exist (mcp.json, README.md, persona.yaml)
- Analyzes MCP configurations - Determines appropriate emoji labels based on server requirements
- Categorizes personas - Places personas in correct README sections based on their purpose
- Updates README table - Adds missing personas to appropriate category tables
- Preserves existing entries - Does not modify existing persona entries, only adds new ones
Emoji Label Detection
The command automatically assigns emoji labels based on MCP server analysis:
- 🔐 Secrets Required - Detects environment variables with credentials/API keys
- 🌐 Remote Services - Identifies cloud services, APIs, and external connections
- 💻 Local Only - No external dependencies or credentials required
- ⚙️ Configuration - Requires environment variable setup
- 🚀 Zero Setup - Works immediately without configuration
- 📦 External Dependencies - Requires additional tools/services
- 🏢 Enterprise - Production/enterprise-focused configurations
Category Assignment
Personas are automatically categorized based on:
- Filename patterns (e.g.,
*-dba,*-sre,*-engineer) - MCP server types (database, cloud, monitoring tools)
- Description keywords from persona.yaml and README.md
- Established patterns from existing personas
Requirements
- Persona must have valid
mcp.json,README.md, andpersona.yaml - README.md must contain a clear description
- persona.yaml should specify the persona's purpose and target audience
Example Output
Found 3 new personas to add:
✓ rust-developer → Software Engineering (💻🚀)
✓ mongodb-dba → Data Science & Analytics (🔐⚙️🏢)
✓ kubernetes-sre → DevOps & Infrastructure (🔐🌐⚙️🏢)
Updated README.md with 3 new personas
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.
- 13d ago First seen · 56 lines · 0 tokens per session scan A f9fe211b77ed
sync-personas 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 488 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.