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 commands/rjmurillo/ai-agents/allgit 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/all)<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/all"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/all.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.00035 | $0.00877 |
| Opus 5 | $0.00017 | $0.00439 |
| Sonnet 5 | $0.00007 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
all 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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Quality Gate - All Agents
Run all 6 quality gate agents (security, QA, analyst, architect, DevOps, and roadmap) sequentially on your current changes.
Pre-flight Checks
Use the Bash tool to gather context:
- Run
git branch --show-currentto determine the current branch - Use $ARGUMENTS as the base branch if provided, otherwise default to
main - Run
git diff "<base_branch>" --name-only | wc -lto count changed files
If no changes detected, exit early with PASS.
Agent Execution
Invoke each agent command using Skill tool and capture results.
Note: The base branch argument is forwarded to each sub-command.
- Security Agent:
/pr-quality:security $ARGUMENTS - QA Agent:
/pr-quality:qa $ARGUMENTS - Analyst Agent:
/pr-quality:analyst $ARGUMENTS - Architect Agent:
/pr-quality:architect $ARGUMENTS - DevOps Agent:
/pr-quality:devops $ARGUMENTS - Roadmap Agent:
/pr-quality:roadmap $ARGUMENTS
Verdict Aggregation
Parse each agent's VERDICT: TOKEN output and merge using these rules:
Merge Logic (canonical: .claude/lib/ai_review_common/verdict.py:merge_verdicts):
- ANY
CRITICAL_FAIL,REJECTED,FAIL,NEEDS_REVIEW, orNON_COMPLIANT→ Final: CRITICAL_FAIL - ANY
WARNorPARTIAL(no critical failures) → Final: WARN - ANY
UNKNOWN(no critical, no warn) → Final: UNKNOWN - ALL
PASSorCOMPLIANT→ Final: PASS - Empty input → Final: UNKNOWN
UNKNOWN downgrades a would-be PASS so a missing or crashed axis cannot silently produce a green verdict. Real WARN and CRITICAL_FAIL findings override UNKNOWN.
Output Summary
Generate consolidated report in EXACTLY this format. Do not add preambles or explanations before the table:
| Agent | Verdict | Status | Key Findings |
|---|---|---|---|
| 🔒 Security | [verdict] | [emoji] | [summary] |
| 🧪 QA | [verdict] | [emoji] | [summary] |
| 📊 Analyst | [verdict] | [emoji] | [summary] |
| 📐 Architect | [verdict] | [emoji] | [summary] |
| ⚙️ DevOps | [verdict] | [emoji] | [summary] |
| 🗺️ Roadmap | [verdict] | [emoji] | [summary] |
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.
- 4d ago First seen · 82 lines · 35 tokens per session scan A bf030e64834f
all is a command published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 877 once invoked, about $0.0002 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-30.
Other commands, from other repositories
load-session
Load a synced session summary for context.
statusline
Configure which sections appear in the Claude Code statusline.
01_confirm
Extract plan from conversation, create file in draft/, auto-apply non-BLOCKING improvements, move to pending.
02_execute
Execute a plan (auto-moves pending to in-progress) with Ralph Loop TDD pattern.
add-integration
Add support for a new service (like Slack, Notion, or GitHub) with full OAuth and API integration.
update-model-rubric
Research the current LLM landscape and update Carmenta's model routing rubrics with latest models, capabilities, and pricing.