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 justnau1020/claude-os --skill fix-issuegit clone --depth 1 https://github.com/justnau1020/claude-osWrote 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/justnau1020/claude-os/fix-issue)<a href="https://agentmods.dev/skills/justnau1020/claude-os/fix-issue"><img src="https://agentmods.dev/badge/skills/justnau1020/claude-os/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/justnau1020/claude-os/fix-issue"><img src="https://agentmods.dev/badge/skills/justnau1020/claude-os/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.00052 | $0.00356 |
| Opus 5.5 | $0.00021 | $0.00142 |
| Sonnet 5.5 | $0.00010 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
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 1mo 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.
What it actually says
Fix GitHub Issue
Fix issue #$ARGUMENTS end-to-end.
Steps
1. Read the issue
gh issue view $ARGUMENTS
Understand the problem, expected behavior, and any reproduction steps.
2. Research the codebase
Find the relevant files using the issue description. Read the code to understand the current behavior and what needs to change.
3. Implement the fix
- Follow the project's existing conventions and patterns
- Make minimal, focused changes -- fix the bug, don't refactor surrounding code
- Add type hints to any new code
4. Write or update tests
- Add a test that would have caught this bug
- Verify existing tests still pass
- Mock external APIs -- no real network calls
5. Verify
Run the project's CI pipeline locally:
# Adjust these commands to match your project's tooling
pytest tests/ -v --tb=short
# lint check
# type check
6. Create a commit
Stage only the files you changed and commit with a message referencing the issue:
Fix #$ARGUMENTS: <brief description of what was fixed>
Do NOT push -- let the user decide when to push.
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.
- 1mo ago First seen · 58 lines · 52 tokens per session scan A df1735d58e84
fix-issue is a skill published in the GitHub repository justnau1020/claude-os (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 356 once invoked, about $0.0002 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-31.
Other skills, from other repositories
semantic-szz-analyzer
Identify bug-introducing commits using semantic analysis that extends traditional SZZ algorithm. Distinguishes semantic changes from refactorings or code movements using control-flow and data-flow similarity analysis. Use when analyzing bug-fix commits to trace back to bug-introducing changes, investigating software…
szz-bug-introducing-commit-identifier
Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining…
git-bisect-assistant
Automatically performs git bisect to identify the first bad commit that introduced a bug or failure. Use when debugging regressions, tracking down when a test started failing, or identifying which commit broke functionality. Handles flaky tests with retry logic and provides comprehensive reports with bisect logs and…
lineage
Use when asked why code exists or why it works the way it does - "why is this here", "why did we pick Y", "who added this and for what", "is it safe to remove", a regression's origin, a magic threshold, or a workaround with no comment - and before deleting or reshaping code whose reason you cannot see.
contributing-upstream
A guide to making useful contributions to an open-source project, including bug reports, minimal examples that reproduce problems, pull requests, contribution rules, licenses, and security disclosures.
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.