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.
git clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote 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/commands/boparaiamrit/skills-by-amrit/fix-issue)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/fix-issue"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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/commands/boparaiamrit/skills-by-amrit/fix-issue"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.00014 | $0.00312 |
| Opus 5 | $0.00007 | $0.00156 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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 10d 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-issue — Fix a Tracked Issue
Fix a GitHub or Linear issue end-to-end.
Instructions
-
Read the issue
$ARGUMENTS:- If it's a number, fetch the issue from the project's issue tracker
- Understand the problem description, acceptance criteria, and any comments
- Check for related issues or PRs
-
Create a branch:
- Branch name:
fix/$ARGUMENTS-short-descriptionorfeat/$ARGUMENTS-short-description - Based on current
mainordevelopbranch
- Branch name:
-
Implement the fix:
- Follow existing code patterns and conventions
- Write the minimal code to fix the issue
- Handle edge cases mentioned in the issue
-
Write tests:
- Add tests that verify the fix
- Include a test for the original failing scenario
- Ensure no regressions
-
Verify:
- All tests pass
- Linting passes
- Build succeeds
-
Commit with a conventional commit message:
fix: short description Fixes #[issue-number] - What was changed and why -
Summarize what was done and what the user should 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.
- 10d ago First seen · 48 lines · 14 tokens per session scan A 23edd7c6312f
fix-issue is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 312 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-31.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.