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 arimxyer/doc-manager-mcp --skill doc-expert-expertisegit clone --depth 1 https://github.com/arimxyer/doc-manager-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/arimxyer/doc-manager-mcp/doc-expert-expertise)<a href="https://agentmods.dev/skills/arimxyer/doc-manager-mcp/doc-expert-expertise"><img src="https://agentmods.dev/badge/skills/arimxyer/doc-manager-mcp/doc-expert-expertise/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/arimxyer/doc-manager-mcp/doc-expert-expertise"><img src="https://agentmods.dev/badge/skills/arimxyer/doc-manager-mcp/doc-expert-expertise.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.00038 | $0.00605 |
| Opus 5 | $0.00019 | $0.00302 |
| Sonnet 5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
doc-expert-expertise 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc-Expert Expertise
These references are the authoritative source for how doc-manager works. Read them for specifics about configuration options, valid values, presets, and syntax.
Quick Reference
| Topic | Reference | When to Use |
|---|---|---|
| Quality criteria | quality-framework.md | Assessing documentation quality |
| Workflows | workflow-sops.md | Executing sync, setup, migration, config tuning |
| Delegation | delegation-protocol.md | Working with doc-writer |
| Releases | release-checklist.md | Pre-release audits |
| Configuration | config-reference.md | Setting up or tuning .doc-manager.yml |
| Conventions | conventions-reference.md | Setting up doc-conventions.yml |
Quality Framework Overview
7 criteria for documentation quality:
- Relevance - Addresses current user needs
- Accuracy - Reflects actual codebase
- Purposefulness - Clear goals and audience
- Uniqueness - No redundancy
- Consistency - Aligned style
- Clarity - Easy to understand
- Structure - Logical organization
See quality-framework.md for scoring rubrics and detailed evaluation guidance.
Workflow Quick Reference
Health Check: detect_changes → report → offer next steps
Full Sync: detect_changes → batch → delegate → validate → assess → baseline
Quality Audit: assess_quality → validate_docs → report → offer fixes
Release Gate: sync(check) → assess_quality → recommendation
Setup: detect_platform → confirm → init → report
Config Tuning: assess_quality → identify project type → recommend strategy/presets → apply → verify
See workflow-sops.md for detailed procedures.
Delegation Quick Reference
When delegating to doc-writer, always provide:
- Context (what changed)
- Platform (formatting)
- File list with source locations
- Conventions
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 67 lines · 38 tokens per session scan A ae3a12cdb533
doc-expert-expertise is a skill published in the GitHub repository arimxyer/doc-manager-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 605 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
writing-release-notes
Use when preparing, refreshing, backfilling, or redrafting a release-notes page under docs/releases/ before opening a normal review pull request.
code-review
Use before opening a pull request, marking one ready for review, or pushing further commits to a branch with an open pull request — or when asked to review a diff or a PR. Reviews the cumulative diff against the project's written commitments and reports evidence-grounded findings; works with any coding agent and needs…
authoring-issues-prs
Use when filing a bug, opening or creating a GitHub issue, drafting an epic or ticket, writing up a finding or review observation worth tracking, or opening a pull request for this repository. Routes the change to the right repo first (library / template / domain), picks the right issue form, links epic children as…
docpull-research
Use the docpull MCP tools (listindexed, ensuredocs, grepdocs, readdoc, fetchurl) to ground answers in real web/source material when the user asks about a specific library, framework, API, vendor, product page, website, or public source URL. Activate on questions like "how do I X in [library]", "what's the API for…
releasing
Use before any release work: the trunk release model, the unstable edge channel, the prepare/release/promotion machinery, release-notes pages, the pre-release artifact smoke test, and, when the plugin channel is enabled, the Claude Code plugin channel.
config-contract
Use when adding a domain configuration field, env var, Dockerfile extension, mcpb install-screen entry, or release-manifest stamp: the sentinel-based config and customization contract.