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 aws-controllers-k8s/ack-dev-skills --skill resolve-issuegit clone --depth 1 https://github.com/aws-controllers-k8s/ack-dev-skillsWrote 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/aws-controllers-k8s/ack-dev-skills/resolve-issue)<a href="https://agentmods.dev/skills/aws-controllers-k8s/ack-dev-skills/resolve-issue"><img src="https://agentmods.dev/badge/skills/aws-controllers-k8s/ack-dev-skills/resolve-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.00061 | $0.04412 |
| Opus 5 | $0.00030 | $0.02206 |
| Sonnet 5 | $0.00012 | $0.00882 |
| Haiku 4.5 | $0.00006 | $0.00441 |
Grade A, and why
resolve-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 6d 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 — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve Issue — ACK Unified Workflow
You take an ACK community GitHub issue and drive it to resolution — all in one pass, no subagents.
Environment Setup
Detect the workspace root automatically. The workspace is the parent directory containing multiple ACK repos (code-generator, runtime, *-controller, etc.).
# Auto-detect workspace: walk up from cwd until we find code-generator or a *-controller dir
ACK_WORKSPACE="$(cd .. && pwd)"
if [[ ! -d "${ACK_WORKSPACE}/code-generator" ]]; then
ACK_WORKSPACE="$(pwd)"
fi
Detect the current GitHub user:
GH_USER="$(gh api user --jq .login)"
Scripts are located relative to this skill file at scripts/.
Shared Scripts
| Script | Purpose | Usage |
|---|---|---|
ensure-repo.sh |
Clone/fork/pull a controller repo | bash scripts/ensure-repo.sh <name>-controller [github-user] [workspace-path] |
regenerate.sh |
Run code generation | bash scripts/regenerate.sh <service> [workspace-path] |
check-breaking-changes.sh |
CRD compatibility check | bash scripts/check-breaking-changes.sh <service> [workspace-path] |
run-tests.sh |
Run unit tests | bash scripts/run-tests.sh <service> [workspace-path] |
All scripts auto-detect ACK_WORKSPACE from $PWD if not passed explicitly.
Phase 1: Triage
Step 1: Fetch and understand the issue
gh issue view $issue --repo aws-controllers-k8s/community --json title,body,labels,comments
Extract:
- Title and body — what is being requested or reported?
- Comments — any additional context, reproduction steps, or clarification from maintainers
- Existing labels — check for
kind/*andservice/*labels - Target controller — from
service/<name>label or by reading the issue body - Resource — mentioned in title/body
If the issue references multiple services, report to user and ask which to focus on.
Step 1.5: Check for out-of-scope (data plane) requests
ACK only manages AWS control plane resources. If the issue requests data plane functionality (reading/writing objects in S3, invoking Lambda, sending SQS messages, querying DynamoDB items, etc.), it is out of scope.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 532 lines · 61 tokens per session scan A 69724998278e
resolve-issue is a skill published in the GitHub repository aws-controllers-k8s/ack-dev-skills (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 4,412 once invoked, about $0.0003 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…