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/leeyudok/agents-scaffold/fix-issuegit clone --depth 1 https://github.com/LeeYudok/agents-scaffoldWrote 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/leeyudok/agents-scaffold/fix-issue)<a href="https://agentmods.dev/commands/leeyudok/agents-scaffold/fix-issue"><img src="https://agentmods.dev/badge/commands/leeyudok/agents-scaffold/fix-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.00003 | $0.00209 |
| Opus 5 | $0.00002 | $0.00105 |
| Sonnet 5 | $0.00001 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
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 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
이슈 #$ARGUMENTS 를 처리한다(이슈 우선 워크플로):
- 이슈 내용 확인 (forge CLI — GitHub
gh issue view, GitLabglab issue view) - 관련 소스 파일 탐색
- 브랜치 생성:
git checkout -b fix/issue-$ARGUMENTS-<요약> - 최소 수정 구현 + 회귀 테스트 작성
- 빌드/테스트 그린 확인(
./gradlew test또는npm test) - 커밋(
#$ARGUMENTS참조) → push → PR/MR 생성 → 머지 - 이슈 클로즈 — forge 규약에 따름(
.claude/rules/forge.md참조)
forge 별 구체 명령은 forge 프리셋이 이 파일을 덮어쓴다.
--forge로 선택.
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 · 17 lines · 3 tokens per session scan A 1b15a1148eb8
fix-issue is a command published in the GitHub repository LeeYudok/agents-scaffold (25 stars, last pushed 5d ago), licensed MIT. It adds 3 tokens to every session and 209 once invoked, about $0.0000 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-30.
Other commands, from other repositories
monitor
Monitor repository health, track issues, and identify maintenance tasks.
set-tracker
Set the issue tracker for the current project.
maggy-init
Interactive wizard that configures Maggy for the user's org, issue tracker, and codebases. Writes /.maggy/config.yaml and ensures deps are installed.
resume-project
Cold-start project — BOARD, PROGRESS, stalled tasks, worktrees.
whats-next
Show current project status and suggest next steps.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.