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 strikersam/autonomous-ai-agency --skill issue-resolvergit clone --depth 1 https://github.com/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/issue-resolver)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/issue-resolver"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/issue-resolver/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/strikersam/autonomous-ai-agency/issue-resolver"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/issue-resolver.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.00000 | $0.00484 |
| Opus 5 | $0.00000 | $0.00242 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
issue-resolver 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 11d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Issue Resolver
Purpose
Provides a structured, repeatable process for resolving GitHub issues from start to finish — reading the issue, planning a solution, implementing it, testing it, and closing it with a proper commit and changelog entry.
When to Use
- When assigned a GitHub issue to implement or fix
- When an issue number is referenced in a task prompt
- When a bug report, feature request, or task needs to be converted into working code
Process
1. Read and Understand the Issue
- Fetch and read the full issue text, including all comments
- Identify: issue type (bug / feature / task / question), acceptance criteria, constraints
- Note any linked issues, PRs, or external references
2. Explore the Codebase
- Identify files relevant to the issue
- Understand existing patterns, conventions, and architecture
- Check if any existing skill applies (e.g.,
auto-fix,implementation-planner,debug-tracer)
3. Plan the Solution
- Write a short implementation plan (can be inline reasoning, not a file)
- Identify edge cases and risks
- Determine what tests are needed
4. Implement
- Make the minimum changes necessary to resolve the issue
- Follow existing code style and conventions
- Do not introduce unrelated changes
5. Test
- Run existing tests; confirm they pass
- Write new tests if the change introduces new behavior
- Manually verify the fix or feature works as intended
6. Document
- Add an entry to
docs/changelog.mdunder[Unreleased] - Update any relevant docs if the issue touched documented behavior
7. Commit and Push
- Write a clear commit message referencing the issue:
fix: resolve #<n> - <short description> - Push to the appropriate branch (master unless otherwise specified)
Output
- Working code changes that resolve the issue
- Passing tests
- Changelog entry
- Clean commit pushed to repository
Notes
- If the issue is ambiguous, implement the most reasonable interpretation and note assumptions in the commit message
- If the issue is out of scope or already resolved, leave a comment explaining why and close it
- Prefer surgical fixes over refactors unless the issue explicitly requests cleanup
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.
- 11d ago First seen · 56 lines · 0 tokens per session scan A a3ebc8573154
issue-resolver is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 484 tokens. 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
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
pr-shepherding
Monitor PR lifecycle from creation through merge including CI monitoring, review comment handling, thread resolution, and merge readiness verification.
agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent - run one issue/PR pipeline on one repository as a supervised fleet. Auto-pick items, preflight every candidate to one deterministic claim verdict, stand up one worker session per item in a dedicated folder, probe them each cycle with one script call…