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 agentmods add skills/soulcodex/agentic/configure-mcpnpx skills add soulcodex/agentic --skill configure-mcpgit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/configure-mcp)<a href="https://agentmods.dev/skills/soulcodex/agentic/configure-mcp"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/configure-mcp.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.00068 | $0.00630 |
| Opus 5 | $0.00034 | $0.00315 |
| Sonnet 5 | $0.00014 | $0.00126 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
configure-mcp 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 5d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure MCP Skill
Guide the user through selecting and configuring an MCP server for their project.
For GitHub issue planning workflows, MCP is the preferred path for issue-backed
plan persistence. If MCP is unavailable or misconfigured, use gh CLI as the
primary fallback.
Step 1 — Understand the Stack
Ask the user:
- What language and framework is the project using?
- What external services or data sources does it interact with? (GitHub, databases, browser automation, documentation lookup, etc.)
- What tasks should the AI agent be able to help with?
Step 2 — Recommend Servers
Based on the stack, recommend from the canonical short-list:
| Server | When to use it |
|---|---|
github |
GitHub repos, issues, PRs, CI status |
filesystem |
Direct file system access within a bounded path |
postgres |
Query and inspect a PostgreSQL database |
context7 |
Live documentation lookup for libraries and frameworks |
playwright |
Browser automation and end-to-end testing |
Explain which servers apply to the user's project and why.
Step 3 — Run the Wizard
Tell the user to run the interactive wizard:
just mcp-add /path/to/project
Walk them through the prompts:
- Enter the server name (e.g.
github) - Choose transport:
stdiofor local executables,httpfor remote servers - Enter the command (e.g.
npx -y @modelcontextprotocol/server-github) - Add environment variables (e.g.
GITHUB_TOKEN) - Confirm the write to
.mcp.json6. Optionally sync to.gemini/settings.json
Step 4 — Verify
After the wizard completes, verify with:
just mcp-list /path/to/project
This should show the newly configured server in the table.
Step 5 — Environment Setup
Remind the user: environment variables referenced in the MCP config (e.g. ${GITHUB_TOKEN}) must be set in the shell before starting the AI tool. They are not stored in .mcp.json — only the variable references are.
Add them to the project's .env or the system environment as appropriate.
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.
- 5d ago First seen · 81 lines · 68 tokens per session scan A 3331bd830e64
configure-mcp is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 630 once invoked, about $0.0003 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-31.
Other skills, from other repositories
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
design-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
design-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
localization-design
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use ux-writing (designer-toolkit).