Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/joshukraine/dotfiles/resolve-issuenpx skills add joshukraine/dotfiles --skill resolve-issuegit clone --depth 1 https://github.com/joshukraine/dotfilesWrote 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/joshukraine/dotfiles/resolve-issue)<a href="https://agentmods.dev/skills/joshukraine/dotfiles/resolve-issue"><img src="https://agentmods.dev/badge/skills/joshukraine/dotfiles/resolve-issue.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00821 |
| Opus 5 | $0.00010 | $0.00411 |
| Sonnet 5 | $0.00004 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
resolve-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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve GitHub Issue
Take a GitHub issue through to a verified, committed implementation on a feature branch — stopping short of the PR.
Fetch — both calls, always
gh issue view $ARGUMENTS # title, labels, body, and a `comments: N` count
gh issue view $ARGUMENTS --comments # the thread — this one omits the body, so it is not a swap for the first
Read the comments, not just the body. The body is the oldest artifact on an issue; comments carry scope added later, sequencing against other issues, and decisions that supersede an acceptance criterion still written in the body. An issue filed months ago and worked today is the normal case, not the exception. Run the second call unconditionally — the comments: N count sits in a metadata header that is easy to skim past, and a zero-comment issue costs one wasted call.
Plan before implementing
Right-size the ceremony to the issue:
- Small and well-scoped (a few files, an obvious approach) — state the plan in a line and proceed. Don't wait for a reply.
- Complex or ambiguous (multiple subsystems, design choices, real risk) — present the implementation plan and wait for explicit approval.
When unsure which applies, treat it as complex and ask.
Branch
Check git branch --show-current first:
- Already on a feature branch for this issue (
<prefix>/gh-$ARGUMENTS-…) — reuse it, do not create a second branch. This includes re-entering this step inside an autopilot fan-out worktree. - Otherwise —
git switch -c <prefix>/gh-$ARGUMENTS-<short-description>
The prefix comes from the issue's type label. If the project defines its own branch convention, that wins.
| Type label | Prefix |
|---|---|
feat |
feat/ |
fix |
fix/ |
chore |
chore/ |
docs |
docs/ |
test |
test/ |
No type label? Bug fixes are fix/, new functionality feat/, everything else chore/.
Commit as you go
Commit each working component rather than everything at the end — typically 3–8 commits for an issue, each one working code.
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 First seen · 73 lines · 21 tokens per session scan A 2111d422ca95
resolve-issue is a skill published in the GitHub repository joshukraine/dotfiles (422 stars, last pushed 22d ago), licensed MIT. It adds 21 tokens to every session and 821 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
review-pr
Review an existing GitHub PR — one verified single-pass read of the diff, inline P1–P3 findings, fixes for the P1/P2s pushed to the PR branch, scoped verification, resolved threads, a summary. Escalates to a two-reader second opinion only for large source changes. Use when asked to review and fix a PR, or to run the…
cmux-fork-session
Fork the current agent session — Claude Code or pi — into a new cmux split pane (or tab): opens a split beside the caller, relaunches this session forked (claude --fork-session / pi --fork), titles it 'fork: ', and keeps that title. Use when the user asks to fork/duplicate/branch the current session into a new split…
cmux-rebuild
Manage the user's durable dev sessions — zellij sessions on remote hosts (bonbon, taffy) reached over mosh, plus the local host's (trifle) own detached zellij sessions, surfaced as cmux tabs via ssh::durable / zellij::resume. Load when the user wants to rebuild/resurrect lost cmux durable surfaces after a cmux restart…
ml-paper-writing
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
python-conventions
Python coding conventions, modern tooling, and project setup. Apply when writing or reviewing Python code, creating projects, writing scripts, or migrating from legacy tools. Covers uv, ruff, ty, type hints, code structure, async, testing, and project configuration.
slidesync
Bidirectional sync between a Slidev markdown deck and Google Slides as native, editable objects (not images). Push markdown -> Slides, pull Slides -> markdown, and round-trip. Use when the user wants to author/version a Google Slides deck from markdown, replicate a deck's styling, or keep a .slidev.md in sync with a…