Borrowing it
Nothing to install: this file belongs to CleanCod3Systems/creator-research-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CleanCod3Systems/creator-research-mcp/main/.agents/skills/add-mcp-tool/SKILL.mdgit clone --depth 1 https://github.com/CleanCod3Systems/creator-research-mcpWrote 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/cleancod3systems/creator-research-mcp/add-mcp-tool)<a href="https://agentmods.dev/skills/cleancod3systems/creator-research-mcp/add-mcp-tool"><img src="https://agentmods.dev/badge/skills/cleancod3systems/creator-research-mcp/add-mcp-tool/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/skills/cleancod3systems/creator-research-mcp/add-mcp-tool"><img src="https://agentmods.dev/badge/skills/cleancod3systems/creator-research-mcp/add-mcp-tool.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.00035 | $0.01082 |
| Opus 5 | $0.00017 | $0.00541 |
| Sonnet 5 | $0.00007 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
add-mcp-tool 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 11d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding an MCP tool to creator-research-mcp
Read AGENTS.md first — this is the step-by-step recipe for its
"MCP tool design conventions" section and its non-negotiable principles (client-reasoning only,
no shared infra, lightweight, never fabricate, English only). Don't build anything here that
contradicts that file; if it seems like it might, stop and ask the user.
This applies regardless of which AI tool or agent you're using — Claude Code, Cursor, Codex, Copilot, or a human contributor reading it directly.
1. Decide where the logic lives
- Pure, testable transformation (stats, clustering, text parsing) → a new file in
packages/core/src/domain/, exported frompackages/core/src/index.ts. No I/O in this layer. - Fetching from a platform →
packages/providers/src/, implementing (a subset of) theContentProviderinterface frompackages/core/src/ports/provider.ts. - The MCP tool itself →
apps/mcp-server/src/tools/<name>.ts, registered inapps/mcp-server/src/server.ts.
Look at apps/mcp-server/src/tools/retention.ts (joins two existing data sources
deterministically) and apps/mcp-server/src/tools/content-ideas.ts (fetches + reuses a cached
repository + calls into a packages/core pure function) as the two reference shapes for a new
tool — most new tools look like one of these two.
2. Write the tool
server.registerTool("tool_name", { title, description, inputSchema }, handler).- Name:
snake_case, verb_noun, under 64 chars. inputSchema: Zod object, every non-obvious field gets.describe(...).description: state the data source, what the tool does NOT do, and any usage hint the model needs at decision time (seeget_transcript's note about grounding scripts in the creator's real voice for the pattern).- Set
annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: false, openWorldHint: true }unless the tool genuinely isn't read-only (nothing in this repo currently isn't). - Errors: return
{ error: "<code>", message: "<human-readable reason>" }as the JSON payload for expected failures (unsupported source, missing data, provider failure) instead of throwing. Reserve throwing/rejecting for genuine programming errors. - Never compute a metric you can't be sure of — return
nullfor that field and push a plain-English reason onto alimitations: string[]array in the payload instead. - If a repository/cache already holds the data (check
content.findIdByHash+ the relevant*Repository.getForItem/get*method inpackages/db/src/repositories.ts), reuse it instead of refetching.
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.
- 11d ago First seen · 80 lines · 35 tokens per session scan A 9cad7df54cb5
add-mcp-tool is a skill published in the GitHub repository CleanCod3Systems/creator-research-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,082 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…