Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheSmokeDev/taskchad-os/master/.claude/commands/github_bug_fix/implement-fix.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/thesmokedev/taskchad-os/implement-fix)<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/implement-fix"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/implement-fix/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/thesmokedev/taskchad-os/implement-fix"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/implement-fix.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.00009 | $0.01286 |
| Opus 5.5 | $0.00004 | $0.00514 |
| Sonnet 5.5 | $0.00002 | $0.00257 |
| Haiku 4.5 | $0.00001 | $0.00129 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Fix: GitHub Issue #$ARGUMENTS
Prerequisites
This command implements fixes for GitHub issues based on RCA documents:
- Working in a local Git repository with GitHub origin
- RCA document exists at
docs/rca/issue-$ARGUMENTS.md - GitHub CLI installed and authenticated (optional, for status updates)
RCA Document to Reference
Read RCA: docs/rca/issue-$ARGUMENTS.md
Optional - View GitHub issue for context:
gh issue view $ARGUMENTS
Implementation Instructions
1. Read and Understand RCA
- Read the ENTIRE RCA document thoroughly
- Review the GitHub issue details (issue #$ARGUMENTS)
- 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
- Check current state of affected files
- Review any recent changes to those files
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 in RCA
- Follow the fix strategy exactly
- Maintain code style and conventions
- Add comments if the fix is non-obvious
c. Handle related changes
- Update any related code affected by the fix
- Ensure consistency across the codebase
- Update imports if needed
4. Add/Update Tests
Following the "Testing Requirements" from RCA:
Create test cases for:
- Verify the fix resolves the issue
- Test edge cases related to the bug
- Ensure no regression in related functionality
- Test any new code paths introduced
Test file location:
- Follow project's test structure
- Mirror the source file location
- Use descriptive test names
Test implementation:
def test_issue_$ARGUMENTS_fix():
"""Test that issue #$ARGUMENTS is fixed."""
# Arrange - set up the scenario that caused the bug
# Act - execute the code that previously failed
# Assert - verify it now works correctly
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.
- 1mo ago First seen · 229 lines · 9 tokens per session scan A a65e4353b7a7
implement-fix is a command published in the GitHub repository TheSmokeDev/taskchad-os (28 stars, last pushed 23d ago), licensed MIT. It adds 9 tokens to every session and 1,286 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-08-30.
Other commands, from other repositories
diagnose
Run a self-check on your AI Brain Starter install (CLAUDE.md, Meta folder, skills, hooks, MCPs).
second-brain-mapping
Map your vault: extract structured metadata from every typed file, surface cross-doc insights, optionally build a knowledge graph.
cierre
A sales call just ended: turn its transcript into the full follow-up (CRM, tasks, email draft, reminder, coaching).
evolve
Cluster hardened instincts into a proposed Command / Skill / Agent (Instinct Engine).
instinct-export
Export this project's instinct library to a portable YAML pack (Instinct Engine).
instinct-import
Import a portable YAML instinct pack with confidence-gated merge (Instinct Engine).