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.
git clone --depth 1 https://github.com/TheDecipherist/claude-code-masteryWrote 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/thedecipherist/claude-code-mastery/pr)<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery/pr"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery/pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery/pr"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery/pr.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00008 | $0.00631 |
| Opus 5.5 | $0.00003 | $0.00252 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (555 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 631 once invoked, about $0.0000 per session on Opus 5.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
worktree
Create a git worktree for isolated feature/fix work.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
commit-claude-config
Un-ignore and commit the kit config (.claude/, CLAUDE.md, .mcp.json, .gitmodules).
git-workflow
Run review, tests, and commit steps, then prepare a pull request.