sync-personas

sync-personas is a command for Claude Code from toolprint/awesome-mcp-personas. It costs 0 tokens per session (488 once invoked), scanned A, original, MIT.

A command that scans a personas directory and updates the top-level README.md with new or missing persona entries. A persona is a predefined assistant setup for a particular role or use case.

In plain words
What is it for?
Use it to validate persona files, inspect their MCP server settings, assign labels for credentials or remote services, categorize personas, and update the README.
Why use it?
It removes the need to find, categorize, label, and format every new persona by hand. It preserves existing entries while adding valid missing ones to the appropriate tables.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to validate persona files, inspect their MCP server settings, assign labels for credentials or remote services, categorize personas, and update the README.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/toolprint/awesome-mcp-personas/sync-personas
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.

agentmods badge for sync-personas

README.md
[![agentmods](https://agentmods.dev/badge/commands/toolprint/awesome-mcp-personas/sync-personas/github.svg)](https://agentmods.dev/commands/toolprint/awesome-mcp-personas/sync-personas)
Your own site
<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.

agentmods 80×15 button for sync-personas

Your own site · 80×15
<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>
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 488 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.

ModelPer sessionOnce 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

Measured 13d ago against content hash f9fe211b77ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

.claude/commands/proj/sync-personas.md · 56 lines

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

  1. Scans personas directory - Discovers all valid persona configurations
  2. Validates persona structure - Ensures required files exist (mcp.json, README.md, persona.yaml)
  3. Analyzes MCP configurations - Determines appropriate emoji labels based on server requirements
  4. Categorizes personas - Places personas in correct README sections based on their purpose
  5. Updates README table - Adds missing personas to appropriate category tables
  6. 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, and persona.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
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.

  1. 13d ago First seen · 56 lines · 0 tokens per session scan A f9fe211b77ed

Subscribe to this mod's changes

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.