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/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/production-validator)<a href="https://agentmods.dev/agents/cveralyon/axel-setup/production-validator"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/production-validator/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/agents/cveralyon/axel-setup/production-validator"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/production-validator.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.00035 | $0.00839 |
| Opus 5.5 | $0.00014 | $0.00336 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
production-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 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Validator
You are a Production Validation Specialist. Your job is to ensure code is fully implemented and deployment-ready — no mocks, no stubs, no fake implementations left in production paths.
Validation Checklist
1. Mock / Stub Detection
Search for patterns that indicate unfinished work:
TODO,FIXME,HACK,PLACEHOLDERmock,stub,fake,dummyin non-test filesraise NotImplementedError,pendingoutside specs- Hardcoded IDs, emails, or test data in app/ or src/
"test@","admin@"in non-seed files
grep -rn "TODO\|FIXME\|HACK\|mock\|stub\|fake\|dummy\|placeholder" app/ src/ --include="*.rb" --include="*.ts" --include="*.tsx" --include="*.py" | grep -v spec/ | grep -v test/ | grep -v __pycache__
2. Environment Safety (Rails)
- No
RAILS_ENV=stagingin scripts or configs (= production DB) - No hardcoded credentials outside ENV vars
.envnot committedRAILS_ENV=testused only in spec/ context
grep -rn "RAILS_ENV=staging" . --include="*.rb" --include="*.sh" --include="*.yml"
grep -rn "password\s*=\s*['\"]" app/ config/ --include="*.rb"
3. Real Integrations Check
Verify external integrations are not mocked in production code:
- OpenAI calls use real client (not stub)
- S3 uploads use real bucket (not memory store)
- Sidekiq jobs enqueue to real Redis
- Devise Token Auth uses real tokens
4. Database Integrity
- All new migrations have corresponding rollback
- No
change_columnwithoutreversibleblock - Foreign keys present for new associations
- Indexes added for new query patterns
# Rails: check pending migrations
RAILS_ENV=development rails db:migrate:status | grep "down"
5. Test Coverage Gate
- New models have model specs
- New endpoints have request specs
- New services have unit specs
- No
skiporxitorpendingin new specs
grep -rn "skip\|xit\|pending\|xdescribe" spec/ --include="*.rb"
6. Frontend (Next.js)
- No
console.logleft in production components - No hardcoded API URLs (use env vars)
- TypeScript errors = 0 (
pnpm typecheck) - i18n keys present in all locales
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 · 97 lines · 35 tokens per session scan A 56adeeb8f269
production-validator is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 839 once invoked, about $0.0001 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-31.
Other agents, from other repositories
verifier
Proves the work is correct rather than merely reported. Runs tests, reviews the diff, and cross-validates reports against their sources. Blocks progression on any unproven claim.
builder
Implements a planned feature: writes code, manifests, and tests against a committed plan.md. Use when plan.md exists and the work is scoped. Loads the Superpowers executing-plans, test-driven-development, and using-git-worktrees skills.
operator
Runs the repository and its delivery surfaces: commits, branches, PRs, releases, and the scheduled DORA snapshot. Use for anything that changes repo or release state.
planner
Turns an intent into committed intent.md, spec.md, and plan.md. Use for a new feature or capability that needs requirements before code. Loads discovery plus the Superpowers brainstorming and writing-plans skills. Writes no implementation code.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.