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/samuelclay/newsblur/commit-update-prgit clone --depth 1 https://github.com/samuelclay/NewsBlurWhat 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.00016 | $0.01046 |
| Opus 5 | $0.00008 | $0.00523 |
| Sonnet 5 | $0.00003 | $0.00209 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
commit-update-pr 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
Commit all staged/unstaged changes, push to remote, create or update the PR, then watch CI until it finishes and fix any failures.
Arguments provided: {{ arguments }}
Steps to execute
-
Check git status to see what changes exist:
git status git diff --stat git diff --staged --stat -
Check for existing PR for the current branch:
gh pr view --json number,title,url,state 2>/dev/null- If a PR exists and is OPEN, note its URL and number - we'll update it
- If no PR exists or it's closed/merged, we'll create a new one
-
Stage all changes (if there are unstaged changes):
git add -A -
Create the commit following the commit message conventions:
- Run
git log --oneline -5to see recent commit style - Run
git diff --stagedto understand the changes - Write a concise commit message summarizing the changes
- Use the format:
git commit -m "$(cat <<'EOF' <commit message here> Co-Authored-By: Claude Opus 4.5 <[email protected]> EOF )"
- Run
-
Push to remote:
git push -u origin HEAD -
Create or update the PR:
If a PR already exists:
- The push already updated the PR
- Note: "Updated existing PR: "
If no PR exists:
- Create a new PR:
gh pr create --title "<title>" --body "$(cat <<'EOF' ## Summary <1-3 bullet points summarizing the changes> ## Test plan - [ ] <testing checklist items> --- Generated with [Claude Code](https://claude.com/claude-code) EOF )"
-
Watch CI and auto-fix failures — do NOT stop after pushing. Monitor the PR's checks until every check has a terminal status (pass, fail, skipped, cancelled), and fix any failures before handing back to the user.
a. Poll for status. After pushing, wait ~30s for CI to register, then:
gh pr checks <PR_NUMBER>The first column is the check name, the second is status (
pending,pass,fail,skipping,cancelled). Re-run this periodically. Do not chainsleepcommands to wait — preferrun_in_backgroundso you don't block, and poll by callinggh pr checksagain on a reasonable cadence (30–60s). Keep going until no check showspending.
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 · 102 lines · 16 tokens per session scan A e981e0f7d7e7
commit-update-pr is a command published in the GitHub repository samuelclay/NewsBlur (7,600 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 1,046 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-08-30.
Other commands, from other repositories
compound
현재 작업에서 재사용 패턴을 추출해 AGENTS.md·문서를 업데이트한다. 같은 종류의 버그·구현을 2회 이상 해결했거나 작업 종료 시 재사용 가치가 보일 때 사용. 일회성 작업에는 쓰지 않는다.
qa
QA 전문가 — 테스트 기획 및 작성. 새 기능에 테스트가 필요하거나 기존 테스트의 신뢰성(Potemkin·Flaky)이 의심될 때 사용. 실제 기능·성능 검증 중심.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
audit
Scan a codebase for existing observability instrumentation and identify gaps.
mobile-verify
Run automated verification loops with pass@k metrics for mobile testing. Executes tests multiple times to detect flakiness.
platform-info
Detect project type (Android/iOS/KMP), list platforms, show platform info, and delegate to appropriate commands.