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/owainlewis/youtube-tutorials/prgit clone --depth 1 https://github.com/owainlewis/youtube-tutorialsWhat 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.00306 |
| Opus 5 | $0.00000 | $0.00153 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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
Pull Request
Push the current branch and open a pull request.
Instructions
- Run
git statusto check for uncommitted changes — commit them first if needed - Run
git log main..HEAD --onelineto see all commits on this branch - Push the branch:
git push -u origin <branch-name> - Create the PR using
gh pr create
PR format
Title
Follow commit format: type(scope): description
Body
## What
1-2 sentences. What does this PR do?
## Why
The problem this solves or the reason for the change.
## How to test
Step-by-step instructions to verify this works.
Rules
- Target branch is
mainunless otherwise specified - PR title should be under 72 characters
- Description should be generated from the actual diff and commit history — not generic
- Include specific test steps, not just "verify it works"
Example
gh pr create \
--title "feat(auth): add password reset flow" \
--body "## What
Adds password reset via email verification tokens.
## Why
Users were permanently locked out after forgetting their password.
## How to test
1. Go to /login and click 'Forgot password'
2. Enter a registered email
3. Check inbox for reset link
4. Follow link and set new password
5. Login with new password"
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 · 56 lines · 0 tokens per session scan A a4caa329911e
pr is a command published in the GitHub repository owainlewis/youtube-tutorials (375 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 306 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
workflow-claude-settings
Track Claude Code settings report changes and find what needs updating.
development-workflows
Update the DEVELOPMENT WORKFLOWS table by researching all 11 workflow repos in parallel.
implement
Execute phased implementation with validation gates.
plan
Create comprehensive planning documentation for a feature.
research
Research and analyze feature viability - GO/NO-GO decision gate.
workflow-claude-commands
Track Claude Code commands report changes and find what needs updating.