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/VoDaiLocz/kilo-kit-mcpWrote 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/commands/vodailocz/kilo-kit-mcp/quality-gate)<a href="https://agentmods.dev/commands/vodailocz/kilo-kit-mcp/quality-gate"><img src="https://agentmods.dev/badge/commands/vodailocz/kilo-kit-mcp/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.1 | $0.00000 | $0.00299 |
| Opus 5 | $0.00000 | $0.00150 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 8d 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.
What it actually says
✅ Quality Gate Command
Usage: Run before every commit to ensure code quality.
Workflow
typecheck → lint → test → build
All gates must pass. No exceptions.
Gates
Gate 1: Pre-Execution
- Intent parsed with confidence > 0.5
- At least one skill matched
- Token budget sufficient
- Required context available
Gate 2: Per-Behavior
- Input validated
- Dependencies satisfied
- No type violations
- Output schema correct
Gate 3: Post-Execution
- All behaviors completed
- No critical errors
- Output meets requirements
- Token usage within estimate ±20%
Gate 4: Pre-Completion (MANDATORY)
- Verify claimed changes exist
- Run relevant tests if applicable
- Check for obvious regressions
- Ensure user request addressed
- Document what was done
Quick Reference
# TypeScript/JavaScript
npx tsc --noEmit && npx eslint . && npm test && npm run build
# Python
mypy . && ruff check . && pytest && python -m build
# .NET
dotnet build && dotnet test
Quality Gate Command v1.0.0
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.
- 8d ago First seen · 56 lines · 0 tokens per session scan A e709d2d2c6d3
quality-gate is a command published in the GitHub repository VoDaiLocz/kilo-kit-mcp (26 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 299 tokens. 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-30.
Other commands, from other repositories
ipd-tr
A command that runs a staged technical review process involving quality, testing, architecture, and requirements checks before a release decision. IPD-OMO is the process named in the add-on; its specialized role names are not explained further in the input.
test-coverage-review
You are an expert QA engineer and testing specialist with deep expertise in test-driven development, code coverage analysis, and quality assurance best practices. Your role is to conduct thorough reviews of test implementations to ensure comprehensive coverage and robust quality validation.
security-review
Complete a security review of the pending changes on the current branch.
code-review
Code review a pull request (local only — never posts to GitHub).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.