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 skills add RaNDoM6913/claude-code-superkit --skill pre-deploy-validatorgit 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/skills/random6913/claude-code-superkit/pre-deploy-validator)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/pre-deploy-validator"><img src="https://agentmods.dev/badge/skills/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/skills/random6913/claude-code-superkit/pre-deploy-validator"><img src="https://agentmods.dev/badge/skills/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.00041 | $0.02383 |
| Opus 5.5 | $0.00016 | $0.00953 |
| Sonnet 5.5 | $0.00008 | $0.00477 |
| Haiku 4.5 | $0.00004 | $0.00238 |
Grade A, and why
pre-deploy-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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Deploy Validator
Determine whether the selected release candidate satisfies its declared pre-deploy checks. Cover compilation, linting, tests, build/bundle, migrations, API spec, debug artifacts, environment configuration, and secrets. Keep the READY / NOT READY verdict and all nine rows; zero reported defects does not establish readiness when required evidence is missing.
Scope, context, and authority
Read applicable AGENTS.md and relevant build, CI, deployment, configuration, and recovery guidance. Establish the requested revision/artifact or working-tree state, deployment target, components, and mandatory criteria. Enumerate every component in the selected deployment, not every project in the repository. Record exclusions and their effect; a partial component check cannot certify the whole release. If release scope or target is unresolved, report that gap instead of selecting an easier target.
Discover actual commands, versions, profiles/features, and expected results from manifests, scripts, CI, and runbooks. A manifest suggests a stack; it does not establish that tools are installed or a conventional command meets the release contract. Prepare a compact matrix of component, check, source/command, mandatory status, and criterion. Represent all nine domains even when justified N/A.
Validate only. Do not fix source/configuration, install/upgrade tools or dependencies, regenerate tracked outputs, apply/rollback migrations, rotate secrets, publish artifacts, start the application/services, or deploy. Inspect command wrappers, lifecycle/setup hooks, and external effects before execution. Existing task authority may permit build/test checks with disposable local output and isolated test fixtures; it does not permit production mutation or a hidden deployment hook. Use installed commands without auto-installing launchers or downloads. Missing required tools, credentials, services, or authority leave an unresolved check; do not hunt for credentials or launch infrastructure to manufacture a result.
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.
- yesterday Changed · -21 lines · +7 tokens per session scan C → A 6c4947d36e20
- 1mo ago First seen · 133 lines · 34 tokens per session scan C 9a9442a0c793
pre-deploy-validator is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,383 once invoked, about $0.0002 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 skills, from other repositories
mcp-dependency-review
Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or other repo-scoped MCP config.
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nav-loop
Run tasks until complete with structured completion signals. Auto-invoke when user says "run until done", "keep going until complete", "iterate until finished", "loop mode", "autonomous mode".
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".
ci-speedup
Cuts the wait from push to green by measuring a pipeline's critical path from run timestamps, then splitting, sharding, trimming setup and sharing test module state, with a before/after ledger. Use when asked to "speed up CI", "CI is slow", "why does a PR take 15 minutes", "CI is the bottleneck", or when agents merge…