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 agentmods add skills/luisfelipemoro/harness-devkit/quality-gatenpx skills add LuisFelipeMoro/Harness-devkit --skill quality-gategit clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkitWrote 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/luisfelipemoro/harness-devkit/quality-gate)<a href="https://agentmods.dev/skills/luisfelipemoro/harness-devkit/quality-gate"><img src="https://agentmods.dev/badge/skills/luisfelipemoro/harness-devkit/quality-gate.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00387 |
| Opus 5 | $0.00028 | $0.00193 |
| Sonnet 5 | $0.00011 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
quality-gate 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 today.
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
Every gate must pass before handoff; a single failing gate blocks the handoff.
Contract
- Input: a working directory containing source code.
- Output: a report table with one PASS/FAIL row per gate plus an overall verdict line.
- Tool boundary: read-only verification; source files stay unmodified, never auto-fixed.
- Done when: the report table prints with an overall verdict line and a coverage figure.
Steps
- Detect the stack from the markers in
references/stack-detection.md. Monorepos match every stack present. - For each detected stack, the gate commands in
references/quality-gate-reference.mdapply in the fail-fast order fromreferences/execution-and-report.md: format, type/vet, lint, build, tests + coverage, race (Go), vulnerability scan. Duplication (≤ 3%) runs once for the whole repo regardless of stack — it is language-agnostic, and a duplicate passes every other gate in the list. - Tests + coverage is the mandatory sensor: every changed source file wants a corresponding test, and coverage below threshold counts as a failing gate.
- The report table and overall verdict line follow the template in
references/execution-and-report.md. The verdict line states PASS when every gate is green.
References
references/stack-detection.md— detection command and file→stack table.references/execution-and-report.md— gate order and report template.references/quality-gate-reference.md— per-stack gate commands and common fixes.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed e54667cab79c
- 4d ago First seen · 24 lines · 57 tokens per session scan A 8ad1d9b7750f
quality-gate is a skill published in the GitHub repository LuisFelipeMoro/Harness-devkit (10 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 387 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…