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/validate-persona)<a href="https://agentmods.dev/commands/toolprint/awesome-mcp-personas/validate-persona"><img src="https://agentmods.dev/badge/commands/toolprint/awesome-mcp-personas/validate-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/validate-persona"><img src="https://agentmods.dev/badge/commands/toolprint/awesome-mcp-personas/validate-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.00367 |
| Opus 5.5 | $0.00000 | $0.00147 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
validate-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.
What it actually says
/validate-persona
Validate and auto-fix a persona package using the persona-engineer agent.
Usage
/validate-persona [persona-name]
Purpose
Delegates to the persona-engineer agent to validate, auto-fix, and report on persona package compliance.
Process
When invoked with a persona name (e.g., /validate-persona simpleton):
- Check if persona exists at
personas/[persona-name]/ - Delegate to persona-engineer agent for comprehensive validation and auto-fixing
- Agent will automatically:
- Validate against schemas
- Research and verify MCP servers
- Fix any issues found
- Generate validation_notes.md
- Report final status
Arguments
[persona-name]- Name of the persona to validate (required)
Implementation
// Pseudocode for command execution
function validatePersona(personaName: string) {
// 1. Verify persona exists
if (!exists(`personas/${personaName}/`)) {
return error(`Persona '${personaName}' not found`);
}
// 2. Delegate to persona-engineer
const agent = loadAgent('.claude/agents/persona-engineer.md');
// 3. Execute validation with auto-fix
const result = agent.validateAndFix(personaName);
// 4. Return result
return result;
}
Notes
- The persona-engineer agent will auto-fix issues without requiring user intervention
- All fixes are documented in
personas/[persona-name]/validation_notes.md - The agent researches actual tool names from MCP server documentation
- No manual approval needed - fixes are applied automatically
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 · 58 lines · 0 tokens per session scan A a5d6ea01e836
validate-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 367 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.
validate-persona compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| validate-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 |