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/farzammohammadi/dev-toolbox/validatorgit clone --depth 1 https://github.com/FarzamMohammadi/dev-toolboxWhat 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.00018 | $0.01698 |
| Opus 5 | $0.00009 | $0.00849 |
| Sonnet 5 | $0.00004 | $0.00340 |
| Haiku 4.5 | $0.00002 | $0.00170 |
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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 273 lines · 18 tokens per session scan A 660d7f375d57
validator is an agent published in the GitHub repository FarzamMohammadi/dev-toolbox (1 stars, last pushed 1mo ago), with no licence file. It adds 18 tokens to every session and 1,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-31.
Other agents, from other repositories
planner
Use for planning intake (core selection, then scope boundary + domain vocabulary or Chain Method brief, depending on core) at the start of a project, and for re-entry when new scope enters play on a project already built or mid-build — including after a build has reached its Stop Condition, where it is the exit…
bootstrap
Use once per invocation, at the start of a new Hedgehog project, to land the workspace for whichever core planner selected at Phase 0 — the first real workspace this project gets, since init with no explicit core flag lands the shared agents/skills/build-graph payload and leaves the workspace to bootstrap. Reads the…
openclaw
OpenClaw is the personal-AI-assistant track of Week 17: an open-source assistant that runs on your devices and meets you in the messaging channels you already use. This guide walks through what it is, how it's architected, how to install and run it, how to point it at a local model, and how to wire it to your Week-16…
research-analyst
Deep web research agent for a specific sub-question. Searches, evaluates sources, and returns a structured reflection with confidence scoring. Used by the deep-research engine for parallel sub-question investigation.
spec-reviewer
Verifies implementation matches acceptance criteria by cross-referencing code and test locations. Validates story format and Definition of Ready compliance. Simple PASS/FAIL classification per criterion.
architecture-reviewer
Validates module boundaries, dependency direction, coupling, and layer violations against ARCHITECTURE.md. Reports only findings with confidence >= 80.