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/nimble-giant/ailloy/start-issuegit clone --depth 1 https://github.com/nimble-giant/ailloyWrote 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/nimble-giant/ailloy/start-issue)<a href="https://agentmods.dev/commands/nimble-giant/ailloy/start-issue"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/start-issue.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.00481 |
| Opus 5 | $0.00000 | $0.00241 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
start-issue 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 4d 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
Start Issue
Fetch a GitHub issue and begin implementation.
Usage
/start-issue <issue-number>
/start-issue <issue-url>
Examples
/start-issue 1234- Start work on issue #1234/start-issue https://github.com/your-org/your-repo/issues/1234- Start work using full URL
Workflow
When this command is used, Claude will:
-
Fetch the issue details using
gh issue view <issue-number> --json title,body,author,state,labels,assignees,milestone,number,url,comments -
Create a todo list with tasks derived from the issue requirements
-
Begin implementation following the issue requirements and acceptance criteria
-
Use issue context to inform commit messages and implementation approach
Scope Boundaries
IMPORTANT: Stay focused on the specified issue ONLY.
- Do NOT search for, fetch, or work on related issues, sub-issues, parent issues, or adjacent issues
- Do NOT follow
#XXXXreferences in the issue body to other issues - Do NOT use
gh issue listorgh issue searchto discover other issues - If the issue description mentions other issues for context, note them but do NOT expand scope to include their requirements
- All work should be scoped strictly to what the specified issue describes
Manual GitHub Issue Commands
Fetching Issue Details
IMPORTANT: Always use --json to avoid GitHub Projects (classic) deprecation errors.
gh issue view <URL or issue-number> --json title,body,author,state,labels,assignees,milestone,number,url,comments
Examples:
gh issue view 1234 --json title,body,author,state,labels,assignees,milestone,number,url,commentsgh issue view https://github.com/your-org/your-repo/issues/1234 --json title,body,author,state,labels,assignees,milestone,number,url,comments
Notes
- Authentication handled through user's GitHub CLI login
- Use
#<issue-number>format in commit messages - Focus on rapid implementation of the single issue
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.
- 4d ago First seen · 59 lines · 0 tokens per session scan A 19a6072acfec
start-issue is a command published in the GitHub repository nimble-giant/ailloy (10 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 481 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.