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.
git clone --depth 1 https://github.com/joshsymonds/nix-configWrote 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/commands/joshsymonds/nix-config/validate)<a href="https://agentmods.dev/commands/joshsymonds/nix-config/validate"><img src="https://agentmods.dev/badge/commands/joshsymonds/nix-config/validate/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/commands/joshsymonds/nix-config/validate"><img src="https://agentmods.dev/badge/commands/joshsymonds/nix-config/validate.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.00005 | $0.00222 |
| Opus 5.5 | $0.00002 | $0.00089 |
| Sonnet 5.5 | $0.00001 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
validate 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.
What it actually says
Implementation Validation
Ultrathink and thoroughly validate the implementation we just completed
Validation Criteria
Start with: "Let me ultrathink about this implementation and examine the code closely"
1. Task Completeness
- All requirements fully implemented
- Edge cases properly handled
- No missing functionality
2. Code Quality
- Idiomatic for the language
- Proper error handling and resource management
- Functions appropriately sized and focused
3. Architecture Integrity
- No duplicate code paths or reinvented wheels
- Consistent with existing patterns
- No over-engineering or unnecessary abstractions
4. Hidden Issues
- Race conditions or concurrency bugs
- Security vulnerabilities
- Performance bottlenecks
- Missing critical test coverage
Response Format
Be direct and honest:
✅ Done Well: Specific achievements ⚠️ Issues Found: Problems with severity 📊 Verdict: Is the implementation truly complete?
If issues exist, offer to fix them immediately.
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 · 43 lines · 5 tokens per session scan A f2f40d7722e3
validate is a command published in the GitHub repository joshsymonds/nix-config (837 stars, last pushed 2d ago), licensed MIT. It adds 5 tokens to every session and 222 once invoked, about $0.0000 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-30.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.