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 skills/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/skills/yonatangross/orchestkit/fix-issue)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/fix-issue"><img src="https://agentmods.dev/badge/skills/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/skills/yonatangross/orchestkit/fix-issue"><img src="https://agentmods.dev/badge/skills/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.06354 |
| Opus 5.5 | $0.00033 | $0.02542 |
| Sonnet 5.5 | $0.00016 | $0.01271 |
| Haiku 4.5 | $0.00008 | $0.00635 |
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 8d 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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Issue
Host-neutral workflow. Invoke by skill name (fix-issue). Claude Code slash routing, YAML hook loaders, and .claude/chain live in 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.
Load the issue the target names first. A fork skill never runs frontmatter hooks (#4683), so fetch ISSUE_NUMBER (the flags-stripped target, never $ARGUMENTS[0]) yourself and keep the result in mind. Do not call skill/issue-context-loader for this: it takes its number from the branch name, not from the argument, so on a branch like fix/ork10-... it loads a different issue. Use the CLI the M122 host note selects (gh, glab, or bb):
What ships with it
23 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/commit-template.md 2.0 KB
- assets/rca-report-template.md 1.3 KB
- assets/runbook-entry-template.md 864 B
- checklists/fix-complete-checklist.md 1.0 KB
- references/agent-selection.md 1.9 KB
- references/agent-teams-rca.md 3.8 KB
- references/cc-enhancements.md 1.3 KB
- references/claude-code.md 1.5 KB
- references/fix-blast-radius.md 2.5 KB
- references/fix-phases.md 8.0 KB
- references/hypothesis-rca.md 2.2 KB
- references/prevention-patterns.md 2.1 KB
- references/similar-issue-search.md 1.9 KB
- rules/_sections.md 1.0 KB
- rules/_template.md 339 B
- rules/evidence-gathering.md 2.5 KB
- rules/rca-fault-tree.md 3.8 KB
- rules/rca-fishbone.md 3.6 KB
- rules/rca-five-whys.md 3.3 KB
- scripts/prior_fix_lookup.py 6.2 KB runs code
- scripts/signature_lib.py 6.0 KB runs code
- scripts/similar-issue-finder.sh 3.4 KB runs code
- test-cases.json 2.5 KB
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.
- 8d ago Changed · +3 lines db480ae60e12
- 17d ago Changed · +2 lines 1f046991111c
- 20d ago Changed 5f6c8baf2f27
- 21d ago Changed · -1 lines 36fe50d60fe6
- 24d ago Changed · +2 lines c325e15f72a8
- 26d ago Changed · +2 lines da8525243e9e
- 27d ago Changed 39961da8df60
- 29d ago Changed f64b24a5a8a9
- 1mo ago Changed · -7 lines 4ef910ffb2ea
- 1mo ago First seen · 483 lines · 82 tokens per session scan A 9fe40856bafe
fix-issue is a skill published in the GitHub repository yonatangross/orchestkit (297 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 6,354 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-09-03.
Other skills, from other repositories
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
resolve-inputs
Select the Resolve mode, recover its input, check the workspace, and discover existing fixes.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.