agentcmd: Command for Claude Code

.claude/commands/fix.md

fix is a command for Claude Code from jnarowski/agentcmd. It costs 11 tokens per session (502 once invoked), scanned A, original, MIT.

A command that runs the validation checks documented in a project's README, then fixes reported errors and warnings until the checks pass.

In plain words
What is it for?
Use it to address type errors, lint warnings, and test failures in a codebase.
Why use it?
It removes the repeated work of finding issues, planning fixes, and rerunning checks by hand.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the TodoWrite tool.

This is jnarowski/agentcmd's own configuration. It tells Claude Code how to work on agentcmd itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentcmd configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jnarowski/agentcmd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jnarowski/agentcmd/main/.claude/commands/fix.md
Clone the repo
git clone --depth 1 https://github.com/jnarowski/agentcmd

Made for: Claude Code.

Wrote 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.

agentmods badge for fix

README.md
[![agentmods](https://agentmods.dev/badge/commands/jnarowski/agentcmd/fix/github.svg)](https://agentmods.dev/commands/jnarowski/agentcmd/fix)
Your own site
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/fix"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/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.

agentmods 80×15 button for fix

Your own site · 80×15
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/fix"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 502 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00502
Opus 5.5 $0.00004 $0.00201
Sonnet 5.5 $0.00002 $0.00100
Haiku 4.5 $0.00001 $0.00050

Measured 2mo ago against content hash 594457cf1dd9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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/fix.md · 56 lines

How it starts

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

Fix

Runs all validation commands found in readme, and automatically fixes all issues including warnings. Iterates until validation passes with no errors or warnings.

Workflow

  1. exceute "pnpm check" - this runs check-types, lint and test

  2. Run Initial Validation

    • Execute the validation command using the Bash tool
    • Capture the full output including errors, warnings, and info messages
    • Parse the output to identify all issues that need fixing
  3. Create Fix Plan

    • Use TodoWrite to create a todo list with all issues found
    • Group similar issues together (e.g., "Fix 5 type errors", "Fix 3 lint warnings")
    • Mark the first issue as in_progress
  4. Fix Issues Automatically

    • Fix all issues without prompting for confirmation, even if they aren't related to code you wrote
    • For each issue or group of issues:
      • Analyze the root cause
      • Apply the fix using appropriate tools (Edit, Write, Bash)
      • Mark the todo as completed
      • Mark the next todo as in_progress
    • Common fix patterns:
      • Type errors: Add type annotations, fix incorrect types, update interfaces. For TypeScript issues that cannot be fixed, use @ts-ignore comments only as a last resort
      • Lint warnings: Format code, remove unused imports, fix style issues
      • Test failures: Update test expectations, fix broken logic, mock missing dependencies
      • Build errors: Fix import paths, resolve missing dependencies, update configs
  5. Verify Fixes

    • Re-run the validation command
    • Check if all issues are resolved
    • If new issues appeared, add them to the todo list and continue fixing
    • Repeat until validation command exits with success (exit code 0)
  6. Report Results

    • Report the total number of issues fixed
    • Show the final validation output
    • List any remaining issues that could not be auto-fixed (if any)

Report

After completion, report:

  1. The validation command that was executed
  2. Number of issues found initially
  3. Summary of fixes applied (grouped by category)
  4. Final validation status (pass/fail)
  5. Full output of the final validation run

Read the full file on GitHub · 56 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.

  1. 2mo ago First seen · 56 lines · 11 tokens per session scan A 594457cf1dd9

Subscribe to this mod's changes

fix is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 502 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-09-01.

Related

fix compared with commands from other repositories

fix next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
fixjnarowski/agentcmdCommand1810mo agoMITA11Claude Code
qa-changesOpenHands/extensionsCommand176yesterdayMITA63Claude Code
react-nativegetsentry/toolkitCommand957yesterdaynoneA0Claude Code
auditar-cascadingluanpdd/kit-mcpCommand54d agoMITA54Claude Code
http-serviceMadAppGang/magusCommand14yesterdayMITA27Claude Code
doctordoncheli/don-cheli-sddCommand592mo agoApache-2.0A76Claude Code
doctorfatihkan/badiCommand71mo agoMITA0Claude Code