Borrowing it
Nothing to install: this file belongs to kimrejstrom/alpacalyzer-algo-trader. 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/kimrejstrom/alpacalyzer-algo-trader/main/.agents/commands/fix-issue.mdgit clone --depth 1 https://github.com/kimrejstrom/alpacalyzer-algo-traderWrote 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/kimrejstrom/alpacalyzer-algo-trader/fix-issue)<a href="https://agentmods.dev/commands/kimrejstrom/alpacalyzer-algo-trader/fix-issue"><img src="https://agentmods.dev/badge/commands/kimrejstrom/alpacalyzer-algo-trader/fix-issue/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/kimrejstrom/alpacalyzer-algo-trader/fix-issue"><img src="https://agentmods.dev/badge/commands/kimrejstrom/alpacalyzer-algo-trader/fix-issue.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.00000 | $0.00609 |
| Opus 5 | $0.00000 | $0.00304 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
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 10d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Issue Command
Fetch issue details, find relevant code, implement fix, and open PR.
Usage
/fix-issue <issue_number>
Arguments:
issue_number: The GitHub issue number to fix
Argument Indexing
- Claude Code: Use
$1for the first argument (issue number) - OpenCode: Use
$ARGUMENTSto get all arguments
Steps
1. Get Repo Info
git remote get-url origin
Parse owner and repo name.
2. Fetch Issue
Use gh CLI to fetch the issue:
gh issue view <issue_number> --repo <owner>/<repo>
3. Analyze Issue
Read the issue description:
- What needs to be fixed?
- What are the acceptance criteria?
- Are there any hints about where the code lives?
4. Find Relevant Code
Search for relevant code:
# Search for keywords
rg "keyword" src/
# Find test files
ls tests/test_*.py
5. Create Branch
git checkout -b fix/issue-<issue_number>-<short-description>
6. Write Test First
Create test that reproduces the issue:
def test_bug_fix():
"""Test for issue #XX"""
# Test that demonstrates the bug
pass
Run test to confirm it fails.
7. Implement Fix
Implement the fix to make the test pass.
8. Run Tests
uv run pytest tests -x -q
9. Run Linting
uv run ruff check .
uv run ruff format .
10. Run Type Checking
uv run ty check src
11. Commit
git add -A
git commit -m "fix(scope): description for #XX"
12. Push and Create PR
git push -u origin fix/issue-XX-description
gh pr create --repo <owner>/<repo> \
--title "fix(scope): description for #XX" \
--head fix/issue-XX-description \
--base main \
--body-file - <<'EOF'
## Summary
<description>
## Issue
Fixes #XX
EOF
13. Trigger Code Review
@code-reviewer Please review:
- ISSUE_NUMBER: <issue_number>
- PR_NUMBER: <pr_number>
- OWNER: <owner>
- REPO: <repo>
- FEATURE_DESCRIPTION: <brief description>
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.
- 10d ago First seen · 143 lines · 0 tokens per session scan A f393742c851d
fix-issue is a command published in the GitHub repository kimrejstrom/alpacalyzer-algo-trader (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 609 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-31.
Other commands, from other repositories
unbloat
Remove dead code, duplicate files, and unused dependencies with user approval at each step. Backs up before deleting.
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
payload-revert
Stage reverts for high-confidence payload candidates identified by payload-analysis.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
CLAUDE
When debugging TUI commands like wt switch (interactive picker), use the tmux-cli skill (preferred) or MCP's node-terminal tools to test interactively.
fix-issue
Analyze and fix the GitHub issue: $ARGUMENTS.