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/docs-rewritenpx skills add pankaj28843/docs-mcp-server --skill docs-rewritegit 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/docs-rewrite)<a href="https://agentmods.dev/skills/pankaj28843/docs-mcp-server/docs-rewrite"><img src="https://agentmods.dev/badge/skills/pankaj28843/docs-mcp-server/docs-rewrite.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.00011 | $0.00083 |
| Opus 5 | $0.00005 | $0.00042 |
| Sonnet 5 | $0.00002 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
docs-rewrite 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 4d 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
Rewrite the specified documentation file following Divio quadrants:
- Determine correct quadrant (Tutorial/How-To/Reference/Explanation)
- Active voice, second person
- Real, runnable examples only
- Cross-reference related docs
- Validate with
uv run mkdocs build --strict
Target file: $ARGUMENTS
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.
- 4d ago First seen · 14 lines · 11 tokens per session scan A 2cac5292f7e1
docs-rewrite is a skill published in the GitHub repository pankaj28843/docs-mcp-server (2 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 83 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.
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.
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.
blameless-postmortem
Write a blameless incident postmortem — timeline, impact, root cause, and concrete follow-ups, focused on systems not people.
design-honest-record-keeping
Use when designing or auditing your organization's documentation practices — to establish institutional norms for recording events, failures, and decisions accurately and without euphemism, because institutions that record reality honestly have better learning loops and accountability than those that soften or omit…