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 commands/arimxyer/doc-manager-mcp/doc-syncgit 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/commands/arimxyer/doc-manager-mcp/doc-sync)<a href="https://agentmods.dev/commands/arimxyer/doc-manager-mcp/doc-sync"><img src="https://agentmods.dev/badge/commands/arimxyer/doc-manager-mcp/doc-sync.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.00006 | $0.00416 |
| Opus 5 | $0.00003 | $0.00208 |
| Sonnet 5 | $0.00001 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
doc-sync 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
Documentation Sync Workflow
Synchronize documentation with code changes.
doc-expert agent Please run a documentation sync workflow.
Execute the full sync process:
- Detect Changes: Run
docmgr_detect_changeswithinclude_semantic=trueto understand what changed - Review Action Items: Use
action_itemsandconfig_field_changesfrom output to prioritize work - Analyze Impact: Identify which documentation files are affected
- Delegate Updates: If changes require documentation updates:
- Batch changes into groups of 10-15 files
- Delegate to doc-writer agent with specific guidance
- Include platform context and conventions
- Validate: After doc-writer agent completes, validate the updates
- Assess Quality: Run quality assessment on updated documentation
- Feedback Loop: If quality issues found, provide feedback and iterate (max 3 iterations)
- Update Baseline: Once quality is acceptable, ask user if they want to update the baseline
- If yes: run
docmgr_sync mode="resync"ordocmgr_update_baseline - If no: report completion without baseline update
- If yes: run
Provide progress updates at each step and a final summary:
## Documentation Sync Complete
**Changes Detected**: {count} files
**Config Field Changes**: {count} fields
**Action Items**: {count} (critical: N, high: N)
**Documentation Updated**: {count} files
**Validation**: {pass | issues_found}
**Quality Score**: {overall_assessment}
**Baseline**: {updated | not_updated}
### Next Steps
- {any manual actions needed}
If no changes detected:
## Documentation Sync
**Status**: Documentation is up to date
**No changes** detected since last sync.
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 · 52 lines · 6 tokens per session scan A 2ff82279de92
doc-sync is a command published in the GitHub repository arimxyer/doc-manager-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 416 once invoked, about $0.0000 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 commands, from other repositories
research-l2
Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…
capture-answer
Ingests an expert's answers to an L2 questionnaire in the abapwiki knowledge base: transforms the answers (filled in the interviews/ file or given verbally) into a canonical citable expert-answer (slices/ /inputs/expert-answers/), moves gaps to 'answered' and closes the questions. Use this skill when the owner/expert…
ingest-l0
L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
lint-audit
Checks the integrity of the abapwiki knowledge base: parseable YAML frontmatter, no broken wikilinks, resolvable [VERIFIED: path:N-M] citations, non-nested confidence tags, drift between wiki and DB, synchronization between canonical agent contracts and the .claude/agents/ copies. Use this skill periodically or after…
query
Queries the abapwiki knowledge base to answer questions about custom ABAP code (what an object does, which tables it uses, who calls it, dependencies, bugs). Navigates index -> package -> pages; can extend the answer with the SAP system via MCP abap-fs in read-only mode, explicitly citing wiki vs. system.