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.
npx skills add paladini/mcp-me --skill setup-profilegit clone --depth 1 https://github.com/paladini/mcp-meWrote 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/skills/paladini/mcp-me/setup-profile)<a href="https://agentmods.dev/skills/paladini/mcp-me/setup-profile"><img src="https://agentmods.dev/badge/skills/paladini/mcp-me/setup-profile.svg" alt="Measured on agentmods" 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.00035 | $0.00467 |
| Opus 5 | $0.00017 | $0.00234 |
| Sonnet 5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
setup-profile 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 6d 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
Setup mcp-me Profile
Guide the user through creating and populating their personal profile.
Prerequisites
- Node.js 20+
npm install -g mcp-meor usenpx mcp-me
Step 1 — Initialize
mcp-me init
Creates ~/.mcp-me/ with YAML templates and .mcp-me.yaml config.
Step 2 — Configure sources
Edit ~/.mcp-me/.mcp-me.yaml and uncomment generators/plugins:
generators:
github: your-username
devto: your-username
plugins:
github:
enabled: true
username: your-username
Step 3 — Generate profile data
mcp-me generate
Pulls data from public APIs listed in .mcp-me.yaml. No API keys needed for most sources.
CLI flags also work as overrides: mcp-me generate --github octocat --devto myuser
Step 4 — Validate
mcp-me validate
Checks all YAML files against the Zod schema.
Step 5 — Start MCP server
mcp-me serve
Defaults to ~/.mcp-me. Override with MCP_ME_PROFILE_DIR or pass a path: mcp-me serve ~/my-profile.
Step 6 — Connect to AI assistant
Add to .cursor/mcp.json or use the one-click install badge from the README:
{
"mcpServers": {
"me": {
"command": "npx",
"args": ["-y", "mcp-me", "serve"]
}
}
}
Profile location
| Method | Path |
|---|---|
| Default | ~/.mcp-me |
| Env var | MCP_ME_PROFILE_DIR=/path/to/profile |
| CLI arg | mcp-me serve /path/to/profile |
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.
- 6d ago First seen · 86 lines · 35 tokens per session scan A e9d43dfc246d
setup-profile is a skill published in the GitHub repository paladini/mcp-me (18 stars, last pushed 26d ago), licensed MIT. It adds 35 tokens to every session and 467 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
best-practices
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.