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/create-ticketsgit clone --depth 1 https://github.com/owainlewis/youtube-tutorialsWrote 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/owainlewis/youtube-tutorials/create-tickets)<a href="https://agentmods.dev/commands/owainlewis/youtube-tutorials/create-tickets"><img src="https://agentmods.dev/badge/commands/owainlewis/youtube-tutorials/create-tickets.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00260 |
| Opus 5 | $0.00000 | $0.00130 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
create-tickets 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 3d 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
Read the spec file at $ARGUMENTS.
Then:
-
Create a parent issue in Linear with the spec title as the issue title and a summary of the spec as the description. Use the team and project specified below, or ask if not clear.
-
For each task in the spec, create a sub-issue linked to the parent via
parentId. Each sub-issue should include:- A clear title matching the task name
- Description with: what to build, which files to touch, how to verify
- A reference to the spec file:
Spec: <path-to-spec> - Appropriate label:
feature,bug,cleanup,tech-debt, ordocs - Priority: 1=Urgent, 2=High, 3=Normal, 4=Low (default to 3 unless the spec says otherwise)
-
Check for file overlaps between tasks. If two tasks touch the same files, either:
- Set a
blockedByrelationship so they run sequentially, or - Flag the overlap and ask how to resolve it
- Set a
-
Print a summary table of all created tickets with their IDs, titles, and any blocking relationships.
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.
- 3d ago First seen · 19 lines · 0 tokens per session scan A 05eca577ab5c
create-tickets is a command published in the GitHub repository owainlewis/youtube-tutorials (375 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 260 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.
workflow-concepts
Update the README CONCEPTS section with the latest Claude Code features and concepts.
research
Research and analyze feature viability - GO/NO-GO decision gate.
agent-collections
Update the AGENT COLLECTIONS table by researching all agent-collection repos in parallel.
workflow-claude-commands
Track Claude Code commands report changes and find what needs updating.
workflow-claude-subagents
Track Claude Code subagents report changes and find what needs updating.