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.
git clone --depth 1 https://github.com/oalders/kitchen-sinkWrote 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/oalders/kitchen-sink/break-into-gh-issues)<a href="https://agentmods.dev/commands/oalders/kitchen-sink/break-into-gh-issues"><img src="https://agentmods.dev/badge/commands/oalders/kitchen-sink/break-into-gh-issues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/oalders/kitchen-sink/break-into-gh-issues"><img src="https://agentmods.dev/badge/commands/oalders/kitchen-sink/break-into-gh-issues.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.01075 |
| Opus 5 | $0.00005 | $0.00537 |
| Sonnet 5 | $0.00002 | $0.00215 |
| Haiku 4.5 | $0.00001 | $0.00108 |
Grade A, and why
break-into-gh-issues 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 9d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Break down the current feature or work into small, manageable GitHub issues.
Label Management: Before using any label that may not exist, create it first using gh label create "<label-name>" --description "<description>" --color "<hex-color>" (the command succeeds either way: creating the label if it doesn't exist, or printing a message if it does).
Decision Criteria
Choose the appropriate approach based on the scope of work:
Use single-issue approach when:
- Estimated changes are <= 400 lines (excluding dependencies, vendor dirs, docs)
- Work can be completed as one logical unit
- Changes are tightly coupled and can't be meaningfully separated
- No opportunity for parallel work
Use multi-issue approach when:
- Estimated changes are > 400 lines (excluding dependencies, vendor dirs, docs)
- Work can be split into independent components
- Multiple developers could work in parallel
- Clear boundaries exist between different parts of the work
Estimating Line Counts
When estimating line counts for issues:
- Exclude:
node_modules, vendor directories, docs - Include: All application code, tests, configuration files
- Quick estimation methods:
- Count files affected x average lines per file
- Reference similar past issues as benchmarks
- Use
git diff --staton comparable changes
Example estimation:
# For a completed feature, check actual line count
git diff --stat <base-branch> <feature-branch> -- . ':(exclude)node_modules' ':(exclude)vendor' ':(exclude)docs'
# Output might show:
# 5 files changed, 287 insertions(+), 45 deletions(-)
# Net change: ~242 lines (fits in single issue)
Common Sections (All Issues)
Every issue should include:
Overview and Goals
Brief description of the feature and what it aims to accomplish
Design Details
Comprehensive design covering:
- Architecture and components
- Implementation approach
- File structure and changes
- Success criteria
Single-Issue Workflow
When work fits within a 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.
- 9d ago First seen · 137 lines · 11 tokens per session scan A b33173240aa8
break-into-gh-issues is a command published in the GitHub repository oalders/kitchen-sink (4 stars, last pushed 9d ago), licensed MIT. It adds 11 tokens to every session and 1,075 once invoked, about $0.0001 per session on Opus 5. 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.
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.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.