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/taskgit 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.00191 |
| Opus 5 | $0.00000 | $0.00096 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
task 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
Task
Execute a single task from a spec file.
Input
$ARGUMENTS: path/to/spec.md TN
Process
- Read the spec file
- Find the specified task
- Review Why, What, Constraints, and Current State for context
- Implement exactly what the task describes — nothing more
- Run the Verify step
Rules
- Only this task — ignore others in the spec
- Only files listed in the task
- No drive-by refactors or additions
- Follow constraints strictly
- Write tests if specified
- Do NOT add dependencies unless specified in Constraints
After Completion
Report:
- What was implemented
- Files created or modified
- Verification result (pass/fail)
- Any issues or blockers
Suggest next step:
- If more tasks remain:
Read spec and implement TN+1 - If all tasks complete: Run Validation section commands
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 · 37 lines · 0 tokens per session scan A de1c73fa1184
task 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 191 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.