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/utensils/claudette/pull-requestgit clone --depth 1 https://github.com/utensils/claudetteWhat 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.00000 | $0.00658 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
pull-request 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 2d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open a pull request for the current branch against main.
Arguments
$ARGUMENTS— Passdraftto create a draft PR (e.g.,/pull-request draft). If omitted, creates a regular PR.
Steps
-
Pre-flight checks — Before opening the PR, ensure the code is ready:
- Detect the project's toolchain from config files (e.g.,
package.json,Makefile,mix.exs,Cargo.toml,pyproject.toml) - Run the project's format command (e.g.,
prettier,mix format,cargo fmt,ruff format) - Run the project's lint command (e.g.,
eslint,mix credo,cargo clippy,ruff check) - Run the project's typecheck command if applicable (e.g.,
tsc --noEmit,mypy,mix dialyzer) - Run the project's test command (e.g.,
jest,mix test,cargo test,pytest) - If any check fails, fix the issues before proceeding
- Detect the project's toolchain from config files (e.g.,
-
Rebase on origin/main — Ensure the branch is up to date:
- Run
git fetch origin main - Run
git rebase origin/main - If there are conflicts, resolve them one file at a time:
- Read the conflicting file to understand both sides
- Apply the correct resolution preserving intent from both branches
- Run
git add <file>andgit rebase --continue
- After rebase, re-run pre-flight checks to ensure nothing broke
- Run
-
Analyze changes — Review all commits on this branch vs
origin/main:- Run
git log origin/main..HEAD --onelineto see all commits - Run
git diff origin/main...HEADto see the full diff
- Run
-
Draft the PR — Prepare the PR title and body:
-
Title: Use a concise, descriptive title (under 70 characters)
-
Body should include these sections:
Summary
A succinct description of what changed and why. Include a mermaid diagram if the changes involve schema changes, new flows, or architectural changes.
Complexity Notes
Flag any areas of complexity, risk, or non-obvious behavior that reviewers should pay close attention to. If there are none, omit this section.
-
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.
- 2d ago First seen · 53 lines · 0 tokens per session scan A 528550d93e65
pull-request is a command published in the GitHub repository utensils/claudette (75 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 658 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
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
brain-stats
Show claudectl brain learning metrics — accuracy, correction rate, and effectiveness.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.