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 skills add tomzx/agents --skill fix-issuegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/fix-issue)<a href="https://agentmods.dev/skills/tomzx/agents/fix-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/fix-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.1 | $0.00034 | $0.01932 |
| Opus 5 | $0.00017 | $0.00966 |
| Sonnet 5 | $0.00007 | $0.00386 |
| Haiku 4.5 | $0.00003 | $0.00193 |
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Issue
Orchestrates a bug fix from issue to PR by delegating to specialized skills:
check-duplicates-- search for duplicate issues and existing fix PRsreproduce-issue-- fetch the issue, create a worktree, reproduce the bug, record a "before" video of the defect, post resultscreate-implementation-- write a regression test, implement the fix, verify tests passvalidate-implementation-- replay the before-command on the fixed code to capture a comparable "after" recording, then present the before/after pair for user sign-off before any PR is openedcreate-pr-- push the branch and open a pull request, embedding the pre-captured before/after pair in a side-by-side section
The before recording (and the manifest naming the demonstration command/URL) flows from reproduce-issue to validate-implementation via /tmp/<owner>/<repo>/<issue-id>/. validate-implementation replays the same command/URL on the fixed code so the two recordings are directly comparable, then writes captured-proof.json, which create-pr consumes. Recording happens before PR creation, at human-review time, so the user can confirm the fix before it is posted.
If duplicates are found or reproduction fails, the workflow stops at the relevant step.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, target the issue from
$ISSUE_NUMBER(and$REPO). ghCLI authenticated with write access to the target repository- A GitHub issue number describing a bug
- Git worktree support (
git worktreeavailable) - Read any files present under
.sdlc/context/and apply any artifact style rules found there
Workflow
/check-duplicates
|
v
Duplicates found?
/ \
No Yes
| |
v v
/reproduce- Stop
issue (comment posted)
|
v
Reproduced?
/ \
Yes No
| |
v v
Record before Stop
(video + manifest (comment posted)
to /tmp/<owner>/<repo>/<issue-id>/)
|
v
/create-implementation
|
v
/validate-implementation
(replays before-command on fixed code,
captures after, presents pair, gets sign-off)
|
v
/create-pr
(embeds pre-captured before/after pair)
|
v
Done (PR ready for review)
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 · 199 lines · 34 tokens per session scan A dfa57ada868c
fix-issue is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 1,932 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
bisect
Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.