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/commitgit 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.00307 |
| Opus 5 | $0.00000 | $0.00153 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
commit 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.
What it actually says
Commit
Stage and commit changes with a well-written message.
Instructions
- Run
git statusandgit diffto understand all changes - Run
git log --oneline -5to match the repo's existing commit style - Group related changes — if there are unrelated changes, separate them into multiple commits
- Stage files individually (no
git add .unless every change belongs together) - Write the commit message
Before committing, check for
- No
.envfiles or secrets - No
console.log/ debug statements - No commented-out code
Message format
type(scope): subject
Body explains WHY this change was needed, not what changed.
The diff shows what changed.
Types
- feat: New feature
- fix: Bug fix
- refactor: Code restructure (not a fix or feature)
- chore: Maintenance, deps, config
- docs: Documentation
- test: Adding or fixing tests
- perf: Performance improvement
Rules
- Subject line: max 72 chars, imperative mood ("add", not "added")
- Body: explain the reasoning, not the mechanics
- One logical change per commit
- Reference issue numbers if applicable
Example
feat(auth): add password reset via email verification
Users were permanently locked out if they forgot their password.
This adds a reset flow using time-limited email tokens.
Closes #234
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 · 55 lines · 0 tokens per session scan A ec727d4ce0dd
commit is a command published in the GitHub repository owainlewis/youtube-tutorials (365 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 307 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.