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/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/pre-deploy-validator)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/pre-deploy-validator"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/pre-deploy-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/random6913/claude-code-superkit/pre-deploy-validator"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/pre-deploy-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.00042 | $0.02208 |
| Opus 5.5 | $0.00017 | $0.00883 |
| Sonnet 5.5 | $0.00008 | $0.00442 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade C, and why
pre-deploy-validator scanned grade C with 1 finding 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
# Extract env var references from source How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Deploy Validator
Pre-production deployment gate: auto-detect the tech stack, run all 9 checks below, and emit a single READY / NOT READY verdict.
Hard Rules
- Run all 9 checks — or mark a check N/A with a reason — BEFORE emitting the verdict. Never stop at the first FAIL.
- Verdict rule: READY = zero FAIL across all 9 rows. NOT READY = one or more FAIL, with every FAIL row enumerated as a blocker. WARNs never block — list them and stay READY.
- Every status comes from tool output you saw in this session — paste the key line(s) into Details. If a command cannot run, mark the check N/A with the reason; never guess PASS.
- Validate only — never fix. Report blockers; do not edit code or delete artifacts.
- Each check gets exactly one status: PASS / FAIL / WARN / N/A. Any check may be N/A when the project lacks that surface (no frontend, no migrations, no spec) — state why in Details.
Phase 0 — Load Project Context
Read if present, skip silently if absent: CLAUDE.md or AGENTS.md (build/test/lint commands, migration format, deployable components). If neither exists, fall back to README.md + directory structure.
Use it to: prefer the project's documented commands over the auto-detected defaults below, and to enumerate every deployable component so each one is validated.
Phase 1 — Detect Stack & Components
Scan the project root to identify components and their verification commands:
go.mod— Go:go vet,go test,golangci-lint(if available)package.json— Node.js/frontend:tsc --noEmit,npm run lint,npm run build,npm testrequirements.txt/pyproject.toml— Python:mypy,ruff/flake8,pytestCargo.toml— Rust:cargo check,cargo clippy,cargo testmigrations/— SQL migrations**/openapi.yaml— API spec
Done when: you have the component list and the command set for checks 1–4.
Phase 2 — Run the 9 Checks
Done when: every one of the 9 rows has exactly one status backed by output you saw.
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 · 190 lines · 42 tokens per session scan C d60cfda9f3ce
pre-deploy-validator is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 2,208 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
test-automator
Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.
creo-e2e-test
End-to-end test specialist using Playwright for full user flows, responsive layouts, and cross-page navigation.
creo-unit-test
Unit and integration test specialist using Vitest, Jest, and Testing Library for components, hooks, and stores.
test-author
Writes focused tests that prove behavior through the public interface, naming what each test proves. Use when adding coverage or writing tests for a bug fix.
integration-checker
Runs once at the end of a project, after all steps complete. Verifies that all pieces connect correctly across step boundaries — exports used, APIs called, data flows end-to-end. Returns a comprehensive integration report.