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/wesammustafa/opencode-primer/prgit clone --depth 1 https://github.com/wesammustafa/opencode-primerWhat 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.00014 | $0.00275 |
| Opus 5 | $0.00007 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
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 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.
What it actually says
Create a pull request from the current branch:
- Read the current state:
!git status --short
!git log main..HEAD --oneline
!git diff main...HEAD --stat
-
Decide on a PR title:
- Match the repo's conventional-commits style (
feat:,fix:,refactor:,docs:, …) - One short sentence, under ~70 chars
- Imperative voice ("Add X" not "Added X")
- Match the repo's conventional-commits style (
-
Write the PR body using this template:
## Summary
<1–3 bullets — what changed and why, not how>
## Test plan
- [ ] <verifiable step>
- [ ] <verifiable step>
- Push the branch if it's not yet on the remote, then create the PR:
git push -u origin HEAD # only if needed
gh pr create --title "<title>" --body "<body>"
- Print the resulting PR URL when done.
Extra context (optional, from the user): $ARGUMENTS
Don't force-push, amend pushed commits, or rebase main into the branch unless explicitly asked.
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 · 42 lines · 14 tokens per session scan A 5e6dc93c8cff
pr is a command published in the GitHub repository wesammustafa/opencode-primer (384 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 275 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
audit-codebase
RTK Codebase Health Audit — 7 catégories scorées 0-10.
codereview
RTK Code Review — Review locale pre-PR avec auto-fix.
test-routing
Test RTK command routing without execution (dry-run) - verifies which commands have filters.
clean-worktrees
Clean all merged worktrees automatically (no interaction).
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.