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/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/pr-quality-gate-spec-compliance)<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/pr-quality-gate-spec-compliance"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/pr-quality-gate-spec-compliance/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/commands/rjmurillo/ai-agents/pr-quality-gate-spec-compliance"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/pr-quality-gate-spec-compliance.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.00000 | $0.02940 |
| Opus 5.5 | $0.00000 | $0.01176 |
| Sonnet 5.5 | $0.00000 | $0.00588 |
| Haiku 4.5 | $0.00000 | $0.00294 |
Grade A, and why
pr-quality-gate-spec-compliance 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 22d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Compliance Review Task
You are running Stage 1 of a two-stage review. Your one job: decide whether this PR's diff actually implements the acceptance criteria of the spec it claims to satisfy. You are not judging code quality, test depth, security, or style. The Stage-2 review axes cover those. You answer one question: does the change do what the spec says it should do?
This axis gates the review. On CRITICAL_FAIL, /review marks every other axis SKIPPED and reports only this verdict. On UNKNOWN (INCONCLUSIVE), /review records Stage 1 and continues to Stage 2; unknown spec coverage must never suppress real Stage-2 findings. A spec failure makes a quality verdict premature: there is no point grading the craft of code that solves the wrong problem.
Context Mode Enforcement (REQUIRED)
The CI harness prepends a CONTEXT_MODE: [full|summary|partial] header to the
context it sends you. Read that header before you decide a verdict. It tells you
how much of the diff you actually received.
full: the complete diff is present.PASS,WARN, andCRITICAL_FAILare all permitted on the merits.summary: only a file list or stat-only summary is present (the PR exceeded the diff-size limit). You did not see the line-level changes.partial: only a bounded slice of the diff is present (for example, the first N lines). You did not see the rest.
When CONTEXT_MODE is not full, you MUST NOT emit PASS. A PASS asserts
evidence you do not have. Emit WARN (or a higher-severity verdict if the
available metadata already shows a problem), state that context was
summary or partial, and name the specific evidence you would need to clear
the PR. Treat a missing or unrecognized CONTEXT_MODE value as not full.
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.
- 22d ago Changed 72030c6891c8
- 1mo ago First seen · 199 lines · 0 tokens per session scan A 10321859a2a2
pr-quality-gate-spec-compliance is a command published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,940 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-09-16.
Other commands, from other repositories
review-deep
Review change vs spec, plan, code quality heuristics, and repo rules; append remediation phase if needed.
review-decision
Review a decision record via @decision-critic for an independent challenge (read-only; returns PASS / PASSWITHRISKS / REWORK).
apply-review-feedback
Classify and apply accepted PR/MR review feedback.
review-remote
Review open PR/MR and publish findings.
upload-report
Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types…
pr
Create/update PR/MR title and description.