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/duplication-scannergit clone --depth 1 https://github.com/Ohswedd/praxisWrote 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/agents/ohswedd/praxis/duplication-scanner)<a href="https://agentmods.dev/agents/ohswedd/praxis/duplication-scanner"><img src="https://agentmods.dev/badge/agents/ohswedd/praxis/duplication-scanner.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.00072 | $0.00598 |
| Opus 5 | $0.00036 | $0.00299 |
| Sonnet 5 | $0.00014 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
duplication-scanner 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 3d 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 hunt duplication, reinvention, and over-engineering, three sides of "don't write code you don't need". Read-only.
For the scope under review (the current change set, or the files assigned to you by a repo-wide scan):
- Verbatim / near-duplicate logic. Search the codebase for existing code that does the same thing as the new code. Report matches with file paths and the specific overlap.
- Reusable primitives ignored. Identify existing functions, helpers, constants, types, or dependencies (including the language stdlib/framework) that the change should have used instead of re-implementing.
- Copy-paste within the change. Flag repeated blocks that should be factored into a shared function.
- Divergent parallel implementations. Flag cases where the change adds a second way to do something the codebase already does one way, causing future drift.
- Over-engineering / speculative code (YAGNI). Flag anything the change adds that no present requirement needs: unused functions, parameters, exports, or branches; abstraction layers, generics, config flags, or extension points added "for later"; and indirection or design patterns heavier than the problem warrants. Name the simpler form it should take.
For each finding, name the concrete existing thing to reuse (1–4) or the simpler form to adopt (5), and where it lives. Distinguish true problems (must fix) from acceptable, intentional repetition or a genuinely-warranted abstraction.
Return PASS, PASS WITH NOTES, or FAIL with cited, actionable findings.
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.
- 3d ago First seen · 48 lines · 72 tokens per session scan A 44548ee3ed78
duplication-scanner is an agent published in the GitHub repository Ohswedd/praxis (1 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 598 once invoked, about $0.0004 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
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
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…
wp-cinematic
Cinematic scroll-driven theme specialist. Reads cinematic-scroll-kit's schemas/scene.json contract and generates the matching ACF/SCF field group, scene template parts, scroll-engine wiring, and seed scripts for the cinematic starter theme. Handles hybrid demos (cinematic reel + trailing flex sections). Owns the…
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
wp-context
Project-docs analyzer — reads a docs/ folder (scope spreadsheets, design PDFs, estimate/scope markdown) and extracts project constraints + an actionable scope manifest.