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/thedecipherist/claude-code-mastery/prgit clone --depth 1 https://github.com/TheDecipherist/claude-code-masteryWhat 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.00008 | $0.00631 |
| Opus 5 | $0.00004 | $0.00316 |
| Sonnet 5 | $0.00002 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate PR Description
Create a comprehensive pull request description based on the branch diff.
Process
1. Gather Context
# Get current branch name
git branch --show-current
# Find base branch (usually main or master)
git remote show origin | grep 'HEAD branch'
# Get all commits on this branch
git log main..HEAD --oneline
# Get the full diff
git diff main...HEAD --stat
git diff main...HEAD
2. Analyze Changes
Categorize the changes:
- Features: New functionality
- Fixes: Bug fixes
- Refactors: Code improvements without behavior change
- Docs: Documentation updates
- Tests: Test additions/changes
- Chores: Dependencies, configs, tooling
3. Generate PR Description
Use this format:
## Summary
[2-3 sentences describing what this PR does and why]
## Changes
- [Bullet point for each logical change]
- [Group related file changes together]
- [Focus on what changed, not how]
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that causes existing functionality to change)
- [ ] Refactor (no functional changes)
- [ ] Documentation update
## Testing
[How was this tested? What should reviewers verify?]
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed
## Screenshots (if applicable)
[Add screenshots for UI changes]
## Checklist
- [ ] My code follows the project's style guidelines
- [ ] I have performed a self-review
- [ ] I have added tests that prove my fix/feature works
- [ ] New and existing unit tests pass locally
- [ ] Any dependent changes have been merged
---
Generated with Claude Code
4. Determine Title
PR title format: type(scope): description
Examples:
feat(auth): add OAuth2 login supportfix(api): handle null response from payment servicerefactor(db): extract query builder into separate module
5. Output
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 · 118 lines · 8 tokens per session scan A 381002bcbed4
pr is a command published in the GitHub repository TheDecipherist/claude-code-mastery (545 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 631 once invoked, about $0.0000 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
maintainer-review-code-review
Review the PR for code quality, CLAUDE.md compliance, project conventions, and bugs (Pi-tuned).
maintainer-review-synthesize
Synthesize findings from all review aspects into a single maintainer-ready review report (Pi-tuned).
review-synthesize
Produce one evidence-based verdict, write the review report humans read, and publish it when the scope is a PR. You are read-only: never modify project files or commit; your only write outside the artifacts directory is the PR comment below. Read-only extends past the repository: a falsifying command creates its own…
triage
Confirm whether the work item still names real current work, choose the kind of reasoning owed next, and stop. Write the decisive evidence and handoff to $ARTIFACTSDIR/triage.md. You assess and route only: the repository must be exactly as you found it when you finish. No one watches the run; the report and your…
review-docs
Find one defect: after this change, someone following the repository's documentation would form a materially wrong expectation or lack a required step. Wrong documentation is worse than missing documentation; unnecessary documentation is maintenance debt. Read-only: never modify files, commit, or post anywhere.
deploy
Deploy Solana program (devnet first, then mainnet).