Borrowing it
Nothing to install: this file belongs to CGSOG-JumpStarts/JumpStart-AutoNav. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CGSOG-JumpStarts/JumpStart-AutoNav/main/.github/skills/quality-gates/SKILL.mdgit clone --depth 1 https://github.com/CGSOG-JumpStarts/JumpStart-AutoNavWrote 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/cgsog-jumpstarts/jumpstart-autonav/quality-gates)<a href="https://agentmods.dev/skills/cgsog-jumpstarts/jumpstart-autonav/quality-gates"><img src="https://agentmods.dev/badge/skills/cgsog-jumpstarts/jumpstart-autonav/quality-gates/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/cgsog-jumpstarts/jumpstart-autonav/quality-gates"><img src="https://agentmods.dev/badge/skills/cgsog-jumpstarts/jumpstart-autonav/quality-gates.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.00068 | $0.01254 |
| Opus 5 | $0.00034 | $0.00627 |
| Sonnet 5 | $0.00014 | $0.00251 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
quality-gates 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 11d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Gates Skill
This skill provides four automated testing strategies that extend the Jump Start framework's quality assurance capabilities. Each strategy addresses a specific gap in the framework's current testing layers.
Tools
1. Secret Scanner (bin/lib/secret-scanner.js)
Layer: Pre-commit / Layer 1 (Schema & Formatting)
Trigger: After agent writes any file to src/, config files, or .env files
Purpose: Prevents accidental commitment of API keys, tokens, passwords, and private keys
echo '{"files":["src/config.js"],"root":"."}' | node bin/lib/secret-scanner.js
When to use:
- Before every commit during Phase 4 implementation
- After generating configuration files
- When processing user-provided credentials or API keys
- As part of CI pipeline quality gates
Input: JSON with files (array of paths), root (project root), config (optional: custom_patterns, allowlist)
Output: JSON with pass (boolean), findings (array of detected secrets with redacted values), critical/high counts
Built-in detection patterns: AWS keys, GitHub tokens, private key headers, API key assignments, password assignments, database connection strings, Slack tokens, Bearer tokens
2. Type Checker (bin/lib/type-checker.js)
Layer: Layer 1 extension (Schema & Formatting)
Trigger: After agent writes TypeScript or Python files to src/
Purpose: Catches interface mismatches and type errors before runtime
echo '{"files":["src/index.ts"],"root":"."}' | node bin/lib/type-checker.js
When to use:
- After writing or modifying TypeScript files
- After writing or modifying typed Python files (mypy/pyright)
- Before marking a task as complete in TODO.md
- As part of milestone verification
Auto-detection: Finds tsconfig.json, jsconfig.json, pyrightconfig.json, mypy.ini, or [tool.mypy]/[tool.pyright] in pyproject.toml
Output: JSON with pass (boolean), findings (array of type errors with file, line, code, severity), checker name
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.
- 11d ago First seen · 127 lines · 68 tokens per session scan A 237120e0ac97
quality-gates is a skill published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 1,254 once invoked, about $0.0003 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 skills, from other repositories
ndv-adversarial
Adversarial testing cognitive module. Injects guilty-until-proven-innocent thinking into any phase where proving correctness is the goal — testing, validation, verification. Source: ndv-tester (Edge).
writing-skills
Use when creating a new forge-skill, editing an existing skill, when planning to contribute to forge-skills, when a session has produced a one-off prompt that should be promoted to a skill, or when verifying a skill works before deployment.
tdd
Use when implementing features or fixing bugs test-first, when user mentions "red-green-refactor", when test discipline is required for a specific task, when incremental-implementation needs TDD enforcement, or when a behavior change needs a failing test before any code is written.
incremental-implementation
Use when .forge/tasks.yaml exists and implementation is starting, when executing a planned task list one task at a time, when a feature must ship in independently-verifiable slices, or when contracts in .forge/contracts/ need to be implemented against acceptance criteria.
seed-data-and-fixtures
Use when creating demo data, test fixtures, seed scripts, or factory functions, when preparing for a sales demo and the screenshots are full of "John Doe", when test data is missing edge cases, or when seed scripts crash on a second run.
debugging-and-recovery
Use when something is broken, a test is failing, behavior is wrong, when investigating a production incident, when a user reports a bug, when a feature works locally but not in another environment, or when the system behaves differently than the contract specifies.