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/mpecan/tokf/implement-issuegit clone --depth 1 https://github.com/mpecan/tokfWhat 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.03101 |
| Opus 5 | $0.00000 | $0.01550 |
| Sonnet 5 | $0.00000 | $0.00620 |
| Haiku 4.5 | $0.00000 | $0.00310 |
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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Issue Workflow
You are orchestrating a Plan → Implement → Review → Remediate → PR cycle for a GitHub issue, with support for stacked PRs when issues form a linear dependency chain.
Input
The user will provide a GitHub issue number: $ARGUMENTS
Phase 1: Load Context & Determine Stacking
- Run the context loader script to fetch all issue data in one shot:
This fetches: issue details, all comments, milestone issues, dependency states, open feat/ PRs, and git state..claude/scripts/load-issue-context.sh <number> - Read CLAUDE.md and MEMORY.md for project conventions
- From the script output, verify all dependencies are complete (closed/merged or open PR in current stack)
Stacking Decision
Determine whether this issue should stack on a previous branch or start fresh from main.
Algorithm:
- Find this issue's position in any implementation sequence
- Look at the previous issue in the sequence (by step number, not by dependency list)
- If the previous issue has an unmerged PR branch that is an ancestor of this issue's dependencies → stack on that branch
- If the previous issue is already merged to main → branch from main
- If this issue has multiple unmerged predecessors on different branches → this is a merge point. STOP and tell the user the predecessor PRs must be merged first.
In practice:
The script output includes an === Open Feature Branches === section listing all open PRs on feat/ branches and their targets. Use this to determine stacking:
# If stacking:
git checkout <predecessor-branch>
git checkout -b feat/<this-issue>
# If fresh from main (works in worktrees where local main may not exist):
git fetch origin main
git checkout -b feat/<this-issue> origin/main
Report the stacking decision to the user:
Stacking: feat/<this-issue> → feat/<predecessor-issue> → ... → main
PR will target: feat/<predecessor-issue>
or:
Fresh branch: feat/<this-issue> from main
PR will target: main
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 · 337 lines · 0 tokens per session scan A 09904a69d535
implement-issue is a command published in the GitHub repository mpecan/tokf (195 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,101 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
benchmark
Explain or summarize Governor vs Caveman performance benchmark results.
compress
Automatically compress CLAUDE.md or other memory files with protected-span safety. One-command token savings.
plan
Create a compact implementation contract before broad app/site/game/refactor work.
audit
Audit recurring context files and suggest usage-limit optimizations.
install-rules
Install Governor compact-mode rule files into a project for Codex, Gemini, Cursor, Windsurf, or Cline.
full
Temporarily ask Governor to avoid compacting tool output for the next diagnostic step.