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/alphacornutum/layercakeWrote 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/alphacornutum/layercake/fix-issue)<a href="https://agentmods.dev/commands/alphacornutum/layercake/fix-issue"><img src="https://agentmods.dev/badge/commands/alphacornutum/layercake/fix-issue/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/alphacornutum/layercake/fix-issue"><img src="https://agentmods.dev/badge/commands/alphacornutum/layercake/fix-issue.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.00008 | $0.00097 |
| Opus 5.5 | $0.00003 | $0.00039 |
| Sonnet 5.5 | $0.00002 | $0.00019 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
fix-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 20d 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
Look at issue #$ARGUMENTS in this repo.
!gh issue view $ARGUMENTS
- Understand the bug from the issue description and comments.
- Trace it to the root cause in the code.
- Fix it with the smallest correct change.
- Write a test that would have caught this bug.
- Verify existing tests still pass.
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.
- 20d ago First seen · 15 lines · 8 tokens per session scan A 74d6971990aa
fix-issue is a command published in the GitHub repository alphacornutum/layercake (0 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 97 once invoked, about $0.0000 per session on Opus 5.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-09-26.
Other commands, from other repositories
verify
Run verification loop to validate implementation.
octo-loop
Your first output line MUST be: 🐙 Octopus Loop Mode.
octo-debug
Debug a symptom through reproducible, bounded evidence.
dart-downstream-fix
fix a DART bug reported through gz-physics or Gazebo.
build-fix
Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.
simplify-fn
Refactor a complex function to reduce cyclomatic complexity.