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/outfitter-dev/blz/implement-issuegit clone --depth 1 https://github.com/outfitter-dev/blzWhat 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.02035 |
| Opus 5 | $0.00000 | $0.01018 |
| Sonnet 5 | $0.00000 | $0.00407 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
implement-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 yesterday.
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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Linear Issue
Instructions:
Context
Linear Team ID: 28630e87-24b7-4401-840b-600703c308fc
Linear Team Name: BLZ
Overview
Orchestrate a complete implementation workflow for the Linear issue using specialized subagents. Follow best practices for investigation, implementation, testing, and quality assurance.
Important
- When working on this issue, ensure that you're using
gtcommands exclusively. - If at any point you encounter errors or unexpected behavior, pause and discuss with the user.
Preparation
-
Look up issue details:
- Use
mcp__linear-server__get_issueto fetch the $ARGUMENTS issue (e.g.,BLZ-123) - Extract the
gitBranchNamefield from the response (e.g.,blz-123-fix-something) - Note any dependencies mentioned in the issue description (links to other issues like "Depends on BLZ-XXX" or "Blocked by BLZ-XXX")
- Use
-
Check dependencies and stack placement:
- Review the Graphite stack: !
gt log short - If issue has dependencies:
- Check if dependency issues are already in the stack (look for their branch names in
gt log short) - Verify dependency branches are below (downstack from) where this work will go
- If dependencies are missing or not yet merged: Inform user that the issue is blocked and suggest implementing dependencies first
- If dependencies are complete: Proceed, ensuring this branch builds on top of them
- Check if dependency issues are already in the stack (look for their branch names in
- Determine stack position:
- If dependencies exist in stack: This branch should be created on top of the highest dependency
- If no dependencies: Can branch from trunk (main)
- Check for related work in stack that this should build upon
- Review the Graphite stack: !
-
Verify branch alignment:
- Check current branch: !
git branch --show-current - Compare with the recommended
gitBranchNamefrom Linear - If
gitBranchNamedoes not match the current branch:- Inform the user of the mismatch
- Consider stack position: Suggest
gt create <gitBranchName>from appropriate parent branch - Example: If building on BLZ-100, suggest:
gt checkout blz-100-some-feature && gt create <gitBranchName> - Wait for user confirmation before proceeding
- If on the correct branch: Verify it's in the right position in the stack (correct parent branch)
- If branch exists but wrong position: Suggest
gt move --onto <parent-branch>to reposition
- Check current branch: !
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.
- yesterday First seen · 223 lines · 0 tokens per session scan A 25ad3b7cec71
implement-issue is a command published in the GitHub repository outfitter-dev/blz (27 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,035 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
CAA-add
Add a valuable fix/insight from this session to the Claude Archive (CAA) — give, score honestly, sync.
CAA-search
Search the Claude Archive (CAA) for scored solutions BEFORE solving — take the best hit, verify, apply.
CAA-add-latest
Instantly archive the LATEST hard-won fix from this session to the Claude Archive (CAA) — zero questions.
template
Manage issue templates for streamlined issue creation.
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
security-review
CWE 기반 보안 검토 + STRIDE 위협 모델링 (v6 - effort:max 강제).