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/evan043/claude-cli-advanced-starter-pack/create-task-list-for-issue.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/create-task-list-for-issue.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/create-task-list-for-issue.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/create-task-list-for-issue.template.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.1 | $0.00000 | $0.02117 |
| Opus 5 | $0.00000 | $0.01059 |
| Sonnet 5 | $0.00000 | $0.00423 |
| Haiku 4.5 | $0.00000 | $0.00212 |
Grade A, and why
create-task-list-for-issue.template 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 5d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Start working on a GitHub issue by number with full workflow type: utility complexity: simple model: haiku argument-hint: allowed-tools:
- Bash
- AskUserQuestion
- Task
/create-task-list-for-issue - Quick Issue Start
Start working on a GitHub issue by number. Confirms details, then runs full /create-task-list workflow.
USAGE
/create-task-list-for-issue 123
/create-task-list-for-issue #45
/create-task-list-for-issue 7
EXECUTION
Step 1: Parse Issue Number
Extract issue number from $ARGUMENTS:
- Strip
#prefix if present - Validate it's a positive integer
If no issue number provided:
→ Use AskUserQuestion: "Which issue number would you like to work on?"
Step 2: Fetch Issue Details
gh issue view [NUMBER] --json number,title,body,createdAt,labels,url
Step 3: Detect Issue Format
Check if the issue body contains BOTH of these indicators of /github-task format:
## Acceptance CriteriaOR## Task Checklistsection## Suggested ImplementationOR## Implementation Approachsection
Set IS_TASK_READY = true if both indicators found, false otherwise.
Step 4: Display Issue Confirmation
If IS_TASK_READY = true:
╔═══════════════════════════════════════════════════════════════╗
║ Issue #[NUMBER] ✓ Task-Ready ║
╠═══════════════════════════════════════════════════════════════╣
║ ║
║ [Issue Title - max 50 chars] ║
║ ║
║ Created: [MM/DD/YYYY] ║
║ Labels: [label1, label2, ...] ║
║ URL: [github url] ║
║ ║
║ Format: Has task checklist - will use existing tasks ║
║ ║
║ Tasks found: ║
║ • [Task 1 from checklist] ║
║ • [Task 2 from checklist] ║
║ • ... ([N] total) ║
║ ║
╚═══════════════════════════════════════════════════════════════╝
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.
- 5d ago First seen · 299 lines · 0 tokens per session scan A 32733e0490d4
create-task-list-for-issue.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,117 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
template
Manage issue templates for streamlined issue creation.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
release-harn
Run the tag-first Harn release workflow.
discover
Search the Everruns(Dev) API catalog for available operations.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".