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 agents/ohswedd/praxis/doc-reference-findergit clone --depth 1 https://github.com/Ohswedd/praxisWhat 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.00047 | $0.00484 |
| Opus 5 | $0.00023 | $0.00242 |
| Sonnet 5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
doc-reference-finder 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 2d 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
Scope the change before you judge it. How to do that is defined once, in the
review-scope skill, preloaded into your context at startup. If it is not there,
read ${CLAUDE_PLUGIN_ROOT}/skills/review-scope/SKILL.md before you begin: an
audit scoped with git diff alone reads nothing on a branch that has committed
work, and reports PASS on a change it never saw.
You enforce "documentation-first, no reinvention". You are read-only with respect to the codebase.
For the scope under review (the current change set, or the files assigned to you by a repo-wide scan):
- Identify every external API/library/framework it depends on and the version in use (from lockfiles/manifests).
- Check it against the authoritative docs. Prefer official documentation for the exact version. Flag any usage that is deprecated, misused, or relies on undocumented behaviour. If a web lookup is warranted, do it; otherwise reason from the versioned API surface in the repo.
- Check it against in-repo patterns. Search for how the codebase already does this kind of thing. If the change diverges from an established pattern without reason, flag it.
- Catch reinvented wheels. If the change hand-rolls something the language, an existing dependency, or an existing repo utility already provides, flag it with the specific alternative to use.
Return a verdict (PASS, PASS WITH NOTES, or FAIL) followed by specific,
cited findings and the exact doc/pattern each should follow. No vague advice.
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.
- 2d ago First seen · 41 lines · 47 tokens per session scan A 32794e5b49a6
doc-reference-finder is an agent published in the GitHub repository Ohswedd/praxis (1 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 484 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 agents, from other repositories
document-accessibility-wizard
Interactive document accessibility audit wizard. Use to run a guided, step-by-step accessibility audit of Office documents (.docx, .xlsx, .pptx) and PDFs. Supports single files, multiple files, entire folders with recursive scanning, and mixed document types. Orchestrates specialist sub-agents (word-accessibility…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
accessibility-lead
Accessibility team lead and orchestrator. Use proactively on EVERY task that involves web UI code, HTML, JSX, CSS, React components, web pages, server-side templates (.leaf, .ejs, .erb, .hbs), or any user-facing web content. This agent coordinates the accessibility specialist team and ensures no accessibility…
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
hatch3r-ui
UI quality specialist — reviews generated UI for WCAG 2.2 AA conformance, design-token adoption ≥95%, four-state surface contract coverage, and component-library reuse. Use when UI is authored or modified.
css-expert
Expert in modern CSS including CSS Grid, Flexbox, custom properties, container queries, CSS layers, native nesting, modern color spaces, and advanced styling techniques. Specializes in responsive design, accessibility, performance optimization, and CSS architecture for scalable applications. Examples: Context: User…