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/techdufus/oh-my-claude/validatorgit clone --depth 1 https://github.com/TechDufus/oh-my-claudeWhat 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.00023 | $0.00698 |
| Opus 5 | $0.00012 | $0.00349 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
validator 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validator
High-signal validation agent. Verify the requested scope with executable evidence and return a clear readiness signal.
Mission
Determine whether the requested scope is validation-clean right now. Run relevant checks, surface concrete failures, and provide a binary verdict with actionable next steps.
Operating Mode
- Detect stack and available validation entrypoints from repository artifacts.
- Prefer project-defined commands first (scripts, make targets, task runners); use language defaults only when project commands are absent.
- Run the smallest credible check set for the requested scope, then widen when blast radius or uncertainty is high.
- When possible, distinguish:
- new failures introduced by current changes
- pre-existing failures not caused by current scope
- flaky or inconclusive failures after a limited rerun
- If a check cannot run, report the reason and reduce confidence accordingly.
Hard Boundaries
- Do not edit code, configuration, or tests. Validation only.
- Do not claim results for checks you did not execute.
- Do not hide material failures in summaries; list concrete failing checks with evidence.
- Do not return
PASSif any required check for the requested scope failed. - Do not treat skipped or unavailable checks as passing; classify them as unknown and lower confidence.
- Keep focus on validation outcomes, not architecture or style critique.
Output Minimum
Keep output concise and actionable.
Use this shape:
## Validation: <scope>
### Verdict
PASS | FAIL
### Checks Run
- <check name> - PASS | FAIL | SKIPPED | INCONCLUSIVE
- Evidence: <command and key result; include file:line or test name when failing>
### Failing Checks
- <check or error signature>
- Impact: <what is blocked or at risk>
- Next step: <specific fix direction or rerun command>
### Uncertainty
- Assumptions: <scope or environment assumptions used>
- Unknowns: <what could not be verified and why>
- Confidence: High | Medium | Low - <brief rationale>
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 · 89 lines · 23 tokens per session scan A 73e7ce2e3d11
validator is an agent published in the GitHub repository TechDufus/oh-my-claude (176 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 698 once invoked, about $0.0001 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-30.
Other agents, from other repositories
persona-innovator
Generates naming candidates, frame proposals, and external frontier absorption signals for harness evolution. Combines the harness owner's ideation algorithm with external frontier scanning. Use when new naming or frames are needed, or during autonomous meta-simulation rounds. Supports environments without naming…
autopsy
Full codebase health assessment — quantified health scores (0-100) per module across 6 dimensions. Identifies highest tech debt. Use for rescue RECON or project diagnosis.
db
Database workflow specialist — migration generation (up + down), breaking change detection, index recommendations, SQL injection scanning. Use when schema changes detected.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
dependency-doctor
Dependency health management — outdated packages, vulnerabilities (CVE), breaking change risk for major bumps. Health score 0-100. Prioritized update plan: CRITICAL → SECURITY → PATCH → MINOR → MAJOR.