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/yu-iskw/coding-agent-fabric/fix-issuenpx skills add yu-iskw/coding-agent-fabric --skill fix-issuegit clone --depth 1 https://github.com/yu-iskw/coding-agent-fabricWrote 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/yu-iskw/coding-agent-fabric/fix-issue)<a href="https://agentmods.dev/skills/yu-iskw/coding-agent-fabric/fix-issue"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/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 | $0.00031 | $0.00629 |
| Opus 5 | $0.00015 | $0.00315 |
| Sonnet 5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
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 3d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix GitHub Issue
Purpose
A complete workflow for fixing GitHub issues from understanding the problem to creating a pull request.
Arguments
$ARGUMENTS: GitHub issue number (e.g.,123or#123)
Workflow
1. Understand the Issue
gh issue view $ARGUMENTS
Analyze:
- What is the reported problem?
- What is the expected behavior?
- What is the actual behavior?
- Are there reproduction steps?
2. Research the Codebase
Search for relevant code:
# Search for keywords from the issue
grep -r "keyword" src/
# Find related files
find . -name "*.ts" | xargs grep -l "relatedTerm"
Understand:
- Which files are involved?
- What is the current implementation?
- Where does the bug originate?
3. Create Feature Branch
git checkout -b fix/issue-$ARGUMENTS-<brief-description>
4. Implement the Fix
Apply the minimum necessary change to resolve the issue:
- Fix the root cause, not symptoms
- Don't refactor unrelated code
- Keep changes focused and reviewable
5. Add/Update Tests
Create tests that:
- Reproduce the original bug (should fail without fix)
- Verify the fix works (should pass with fix)
- Cover edge cases
6. Verify the Fix
Run the verification cycle:
pnpm lint
pnpm test
pnpm build
Or invoke the verifier subagent for comprehensive validation.
7. Commit Changes
git add <specific-files>
git commit -m "fix(scope): brief description
Fixes #$ARGUMENTS"
8. Create Pull Request
git push -u origin HEAD
gh pr create --title "fix(scope): description" --body "$(cat <<'EOF'
## Summary
Fixes #$ARGUMENTS
## Problem
[Description of the issue]
## Solution
[How this PR fixes it]
## Testing
- [ ] Added test case for the bug
- [ ] All tests pass
- [ ] Manually verified the fix
## Changes
- [List specific changes]
EOF
)"
Quick Reference
| Task | Command |
|---|---|
| View issue | gh issue view <number> |
| List issues | gh issue list |
| Create branch | git checkout -b fix/issue-<n>-<desc> |
| Link PR to issue | Include Fixes #<n> in commit message |
| Close issue via PR | Include Closes #<n> in PR body |
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.
- 3d ago First seen · 127 lines · 31 tokens per session scan A 56758a3fecfd
fix-issue is a skill published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 19d ago), licensed Apache-2.0. It adds 31 tokens to every session and 629 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-08-31.
Other skills, from other repositories
delegate-coding-agent
Route coding work to another local coding-agent CLI through the llm-provider MCP server. Use when a task benefits from a powerful model for difficult reasoning or a faster, lower-cost model for bounded implementation, tests, investigation, or review.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.