What is implement-fix?

A command that implements the fix described in a root-cause analysis (RCA) document for a GitHub issue.

Use it after an RCA to review the analysis, verify the affected files, apply the proposed fix, follow project conventions, and meet its testing requirements.

It connects an investigated issue to its implementation while checking that the issue still exists and that the current code has not changed unexpectedly.

implement-fix — Command by coleam00

Install

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.

agentmods

npx agentmods add commands/coleam00/archon/implement-fix

Clone the repo

git clone --depth 1 https://github.com/coleam00/Archon

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 864 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00009	$0.00864
Opus 5	$0.00005	$0.00432
Sonnet 5	$0.00002	$0.00173
Haiku 4.5	$0.00001	$0.00086

Measured 2d ago against content hash 4529edd0e008, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement-fix 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 2d 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.

.claude/commands/github_bug_fix/implement-fix.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement Fix: GitHub Issue #$ARGUMENTS

Prerequisites

RCA document exists at .agents/rca/issue-$ARGUMENTS.md
If not, run /rca $ARGUMENTS first

RCA Document to Reference

Read RCA: .agents/rca/issue-$ARGUMENTS.md

Optional — View GitHub issue for latest context:

gh issue view $ARGUMENTS

Implementation Instructions

1. Read and Understand RCA

Read the ENTIRE RCA document thoroughly
Understand the root cause
Review the proposed fix strategy
Note all files to modify
Review testing requirements

2. Verify Current State

Before making changes:

Confirm the issue still exists in current code
Check current state of affected files
Review any recent changes to those files since RCA was written

3. Implement the Fix

Following the "Proposed Fix" section of the RCA:

For each file to modify:

a. Read the existing file

Understand current implementation
Locate the specific code mentioned in RCA

b. Make the fix

Implement the change as described
Follow the fix strategy exactly
Maintain Archon coding conventions (see CLAUDE.md)
Respect package boundaries
Use proper import patterns (import type for type-only)

c. Handle related changes

Update related code affected by the fix
Ensure consistency across packages
Update imports if needed

4. Add/Update Tests

Following the "Testing Requirements" from RCA:

Important Archon test patterns:

Use spyOn() for internal module mocking (not mock.module() unless absolutely necessary)
If adding mock.module(), check if the test file needs its own batch in package.json
Place tests alongside source files or in existing test directories
Follow existing test patterns in the affected package

5. Run Validation

bun run type-check
bun run lint
bun run test
bun run validate

If validation fails:

Fix the issues
Re-run validation
Don't proceed until all pass

6. Verify Fix Manually

If applicable:

Follow reproduction steps from RCA
Confirm issue no longer occurs
Test edge cases
Check for unintended side effects

Read the full file on GitHub · 154 lines

Changes

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.

2d ago First seen · 154 lines · 9 tokens per session scan A 4529edd0e008

Subscribe to this mod's changes

implement-fix is a command published in the GitHub repository coleam00/Archon (23,339 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 864 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.

Git and workflow ai automation bun claude cli coding-assistant

implement-fix