Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yonatangross/orchestkitnpx agentmods add commands/yonatangross/orchestkit/fix-issueWrote 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/yonatangross/orchestkit/fix-issue)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/fix-issue"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/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/yonatangross/orchestkit/fix-issue"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/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.00082 | $0.06289 |
| Opus 5.5 | $0.00033 | $0.02516 |
| Sonnet 5.5 | $0.00016 | $0.01258 |
| Haiku 4.5 | $0.00008 | $0.00629 |
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 5d 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/fix-issue/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Fix Issue
Host-neutral workflow. Invoke by skill name (fix-issue). Claude Code slash routing, YAML hook loaders, and .claude/chain live in skills/fix-issue/references/claude-code.md.
Systematic issue resolution with hypothesis-based root cause analysis, similar issue detection, and prevention recommendations.
Quick Start
fix-issue 123
fix-issue 456
Opus 5.5: Root cause analysis uses native adaptive thinking. Dynamic token budgets scale with context window for thorough investigation.
CC ≥ 2.1.119 multi-host note (M122): Issue fetching works against GitHub, GitLab, Bitbucket, and GitHub Enterprise. The argument is either a numeric ID (use the configured default remote's host) or a full URL (parsed via
parsePrUrl/parseIssueUrlfromsrc/hooks/src/lib/pr-host-parser.ts). Branch on the detected host family for the right CLI:gh issue view(GitHub/GHE),glab issue view(GitLab),bb issue view(Bitbucket). Reference:src/skills/chain-patterns/references/pr-from-platform.md.
Argument Resolution
Check the target first, before any other step. This skill forks and cannot see the conversation. Load Read("../../shared/rules/target-resolution.md"): if the target, flags stripped, is a bare pronoun or deictic (this, them, that one) or empty, return exactly TARGET_UNRESOLVED: <word> and stop. The caller resolves it and re-invokes.
ISSUE_NUMBER = "$ARGUMENTS" with the flags stripped # the target the check above reads, e.g. "123"
# $ARGUMENTS contains the full argument string and may open with flags
# like --model=opus; indexing [0] would fetch the flag, not the issue.
# If the stripped target is not an issue number or URL, return
# TARGET_UNRESOLVED: <word> and stop.
STEP -1: MCP Probe + Resume Check
Run BEFORE any other step. Detect available MCP servers and check for resumable state.
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.
- 5d ago Changed · +10 lines 6722addf02d5
- 17d ago Changed 192a0b10f2eb
- 21d ago Changed · +2 lines 465db0c3732c
- 23d ago Changed · +2 lines fd390150d363
- 24d ago Changed 6c65c518930b
- 1mo ago Changed · +2 lines ef94e16a7534
- 1mo ago Changed 3d402f61bf61
- 1mo ago First seen · 459 lines · 82 tokens per session scan A 5d49965bf35f
fix-issue is a command published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 6,289 once invoked, about $0.0003 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.