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/validate-pr-descriptiongit 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/validate-pr-description)<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/validate-pr-description"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/validate-pr-description.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.00022 | $0.00372 |
| Opus 5 | $0.00011 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
validate-pr-description 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
Validate PR Description Command
Context
- PR title: [User provides]
- PR body: [User provides text or path to a file]
Your task
Validate the PR description against these standards:
1. Conventional Commit Title
Title must match <type>(<scope>)?: <description> where type is one of:
feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert.
2. Issue Linking Keywords
Body should contain at least one issue linking keyword:
Closes #N, Fixes #N, Resolves #N (and their past-tense variants).
These keywords auto-close the linked issue when the PR merges on platforms that support them (GitHub, GitLab). On other platforms (Azure DevOps, Bitbucket), they serve as traceability markers.
3. PR Template Compliance
Check that required sections are populated:
- Summary (non-empty)
- Changes (at least one item)
- Type of Change (at least one checkbox marked)
Validation Script (optional)
If .claude/skills/github/scripts/pr/validate_pr_description.py exists, run it:
uv run python .claude/skills/github/scripts/pr/validate_pr_description.py \
--title "[title]" \
--body-file "[path-to-body.md]"
Otherwise, validate manually against the criteria above.
Report findings with actionable recommendations for any failures.
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 First seen · 54 lines · 22 tokens per session scan A a77b04b081da
validate-pr-description is a command published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 372 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
load-session
Load a synced session summary for context.
02_execute
Execute a plan (auto-moves pending to in-progress) with Ralph Loop TDD pattern.
update-model-rubric
Research the current LLM landscape and update Carmenta's model routing rubrics with latest models, capabilities, and pricing.
update-image-rubric
Research the current image generation landscape and update Carmenta's image model routing rubrics with latest models, capabilities, and pricing.
documentation-audit
Audit documentation for consistency across docs/, knowledge/ specs, and feature-catalog.ts - find gaps, misleading claims, and sync issues.
dev-server
Start a fresh Next.js dev server with intelligent state management - handles port detection, cleanup, and optional browser opening.