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 Detective-XH/DocGraph --skill code-doc-drift-auditgit clone --depth 1 https://github.com/Detective-XH/DocGraphWrote 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/detective-xh/docgraph/code-doc-drift-audit)<a href="https://agentmods.dev/skills/detective-xh/docgraph/code-doc-drift-audit"><img src="https://agentmods.dev/badge/skills/detective-xh/docgraph/code-doc-drift-audit/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/detective-xh/docgraph/code-doc-drift-audit"><img src="https://agentmods.dev/badge/skills/detective-xh/docgraph/code-doc-drift-audit.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.00062 | $0.00948 |
| Opus 5.5 | $0.00025 | $0.00379 |
| Sonnet 5.5 | $0.00012 | $0.00190 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
code-doc-drift-audit 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 1mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs-Code Drift Audit
Invocation — Claude Code:
Skill("code-doc-drift-audit")| OpenCode / Codex: use triggers above.
Runs the DocGraph docs-code drift audit and presents findings for human review. The audit is advisory — findings highlight candidates for action, not authoritative rulings.
Execution
- Model: Haiku (query) → Sonnet (remediation suggestions if requested)
- Effort: Low
- Advisor: Not required
- Core computation: done by DocGraph's
GetDriftFindingsengine, not by this skill
Step 1: Check prerequisites
docgraph_status
Confirm:
code_docpack is listed under Domain Packs and is enabled- At least one
code_filenode is indexed (check node count or rundocgraph_search kind=code_file)
If code_doc is not enabled, tell the user to run:
docgraph pack enable code_doc <project-path>
# or for workspace mode:
docgraph pack enable --workspace code_doc <workspace-path>
Then wait for the sync to complete before proceeding.
Step 2: Run the drift audit
docgraph_context task="docs-code drift audit" format=drift_audit
This calls DocGraph's GetDriftFindings engine, which checks (code_doc findings only):
| Code | Severity | Meaning |
|---|---|---|
code.missing_symbol |
warning | A doc links to a code file path that is not indexed — broken doc-to-code reference |
code.undocumented_export |
info | A code file has no incoming references, wikilinks_to, or related_to edges from any doc — no documentation points to it |
code.unanchored_feature |
info | An approved or review-status doc has no outgoing edge to any indexed code file — feature doc not connected to implementation |
If code_doc is disabled, the output will show zero code.* findings regardless of repo content.
Step 3: Present findings to the user
Group findings by code, severity first (warnings before info).
For each finding:
- State the file path(s) and finding code
- Show the message and evidence from the finding
- Suggest a concrete remediation (below) — but do NOT make the change without confirmation
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.
- 1mo ago First seen · 113 lines · 62 tokens per session scan A 3f5ccbcb6d5e
code-doc-drift-audit is a skill published in the GitHub repository Detective-XH/DocGraph (8 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 948 once invoked, about $0.0002 per session on Opus 5.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
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
okf-loom
Load this repo skill when working with Open Knowledge Format (OKF) bundles: validate, search, discover, update, render, serve the live studio, author concepts, or use the bundled OKF docs. The repo is the distribution unit; run scripts from the checkout with scripts/okf-loom.
tela-wiki
Use when the user asks something their team's own documentation would answer, or asks to write or update a page, spreadsheet, or slide deck in their tela wiki.
document-as-you-go
Quando você termina uma tarefa/commit, pague a dívida de documentação da wiki antes de fechar. Use este skill no Claude Code, OpenCode, Codex CLI ou qualquer agente que tenha a skill MCP do livewiki.
bootstrap-wiki
Bootstrap a repository's initial livewiki documentation through MCP when no wiki pages exist or the user explicitly asks for its first full wiki. Use for deliberate, long-running initial documentation.
context-atlas
Retrieve and interpret durable, evidence-backed project memory from Context Atlas, including overviews, architecture, chronology, decisions, risks, provenance, health, and task-specific context packs. Use when Codex must onboard to an unfamiliar repository, explain how or why code evolved, prepare context before a…