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/pankaj28843/docs-mcp-server/clean-refactornpx skills add pankaj28843/docs-mcp-server --skill clean-refactorgit clone --depth 1 https://github.com/pankaj28843/docs-mcp-serverWrote 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/pankaj28843/docs-mcp-server/clean-refactor)<a href="https://agentmods.dev/skills/pankaj28843/docs-mcp-server/clean-refactor"><img src="https://agentmods.dev/badge/skills/pankaj28843/docs-mcp-server/clean-refactor.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 | $0.00015 | $0.00136 |
| Opus 5 | $0.00008 | $0.00068 |
| Sonnet 5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
clean-refactor 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.
What it actually says
Principles
- Zero behavior changes - only structural improvements
- Tests must pass before AND after
- Minimize rename/reordering churn unless clarity win is undeniable
Steps
- Run baseline tests:
timeout 120 uv run pytest -m unit --no-cov - Apply structural changes (renames, moves, simplifications)
- Run tests again - must be identical pass/fail
- Run
uv run ruff format . && uv run ruff check --fix . - Report what changed and why it's cleaner
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 · 17 lines · 15 tokens per session scan A a0ac71fb7108
clean-refactor is a skill published in the GitHub repository pankaj28843/docs-mcp-server (2 stars, last pushed 7d ago), licensed MIT. It adds 15 tokens to every session and 136 once invoked, about $0.0001 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
rival-search-mcp
Deterministic deep research via RivalSearchMCP. 9 tools: 5-engine web search (DuckDuckGo/Bing/Yahoo/Mojeek/Wikipedia), 9-platform social search (Reddit/HN/StackOverflow/Dev.to/Medium/ProductHunt/Bluesky/Lobste.rs/Lemmy), 5-source news (Google/Bing/Guardian/GDELT/DDG), 5 academic DBs…
code-review
Review code changes, pull requests, branches, commits, and diffs in the Terragrunt MCP Server. Use when asked for a code review, PR review, regression analysis, risk assessment, review comments, or merge-readiness check.
apply-distributed-team-practices
Use when managing a team where members work in different locations, time zones, or on hybrid schedules — to adapt management practices so remote members have equal access to information, relationships, and advancement opportunities as in-office members.
run-performance-improvement-plan
Use when a direct report has a documented pattern of performance falling below role expectations — after informal feedback has not produced sustained change — to create a structured, time-bound plan with clear success criteria before making a continuation decision.
blameless-postmortem
Write a blameless incident postmortem — timeline, impact, root cause, and concrete follow-ups, focused on systems not people.
technical-design-doc-creator
Creates comprehensive Technical Design Documents (TDD) following industry standards with mandatory sections, optional sections, and interactive gathering of missing information.