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-observability)<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/pr-quality-gate-observability"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/pr-quality-gate-observability/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-observability"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/pr-quality-gate-observability.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.02279 |
| Opus 5 | $0.00000 | $0.01140 |
| Sonnet 5 | $0.00000 | $0.00456 |
| Haiku 4.5 | $0.00000 | $0.00228 |
Grade A, and why
pr-quality-gate-observability 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Review Task
You are reviewing a pull request for observability: can an operator understand what the new code does in production from its external outputs?
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.
This is a manipulation-resistance control: an adversary can craft a PR that
trips summary mode to hide a change behind a stat-only context. Forbidding PASS
keeps that change from passing on absent evidence. See
.agents/governance/AI-REVIEW-MODEL-POLICY.md ("CONTEXT_MODE Header (REQUIRED)").
Grounding Rules
- Do NOT claim software versions are "beta", "unstable", or "unreleased" based on training data. Your training data has a cutoff and may be outdated.
- Do NOT claim tools (ruff, mypy, pytest, etc.) lack support for a version unless you have concrete evidence from the diff itself.
- For dependency update PRs: evaluate the diff for internal consistency, not external ecosystem assumptions. If CI tests pass, the tooling works.
- Base findings on what the code shows, not on recalled release schedules.
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 First seen · 185 lines · 0 tokens per session scan A 931e875f98d9
pr-quality-gate-observability is a command published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,279 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-07.
Other commands, from other repositories
session
Complete guide to managing pair programming sessions.
reviewer
Code review using batch file analysis for comprehensive reviews.
pr-enhance
Command "pr-enhance" from airmcp-com/mcp-standards, covering pr-enhance, usage, options, examples and enhance pr.
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.
specify
Create or update the feature specification from a natural language feature description.