Borrowing it
Nothing to install: this file belongs to band-app/band. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/band-app/band/main/.claude/skills/implementation-agent/SKILL.mdgit clone --depth 1 https://github.com/band-app/bandWrote 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/band-app/band/implementation-agent)<a href="https://agentmods.dev/skills/band-app/band/implementation-agent"><img src="https://agentmods.dev/badge/skills/band-app/band/implementation-agent/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/band-app/band/implementation-agent"><img src="https://agentmods.dev/badge/skills/band-app/band/implementation-agent.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.00076 | $0.02006 |
| Opus 5.5 | $0.00030 | $0.00802 |
| Sonnet 5.5 | $0.00015 | $0.00401 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
implementation-agent 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 25d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Agent
Implements a GitHub issue in a Band worktree. Each run does one piece of work: reads progress from the GitHub issue comment, picks the next task, implements it, commits, pushes, and updates progress. Designed to be called repeatedly — each invocation gets fresh context and picks up where the last one left off.
Prerequisites
- Inside a Band worktree (git worktree managed by Band)
ghCLI authenticated with GitHubbandCLI available- Branch name encodes the issue number:
<issue-number>-<summary>(e.g.,99-task-loop-mode)
Steps
1. Detect Issue and Repo
BRANCH=$(git branch --show-current)
ISSUE_NUMBER=$(echo "$BRANCH" | grep -oE '^[0-9]+')
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
If no issue number is found in the branch name, check the task prompt for a #<number> reference. If still not found, skip issue tracking and just work from the prompt.
Fetch the issue:
gh issue view $ISSUE_NUMBER --repo $REPO
2. Read Progress State
Check for an existing progress comment on the issue:
gh api repos/$REPO/issues/$ISSUE_NUMBER/comments \
--jq '.[] | select(.body | contains("## Implementation Progress")) | {id, body}'
Also check the worktree state:
git log --oneline main..HEAD # What's been committed
git status --porcelain # Any uncommitted work
gh pr list --head $BRANCH --repo $REPO --json number,state,reviewDecision # Existing PR?
3. Route by Current State
Based on what you find, take the appropriate action:
State A — PR exists and is approved: Go to step 8 (Merge and Clean Up).
State B — PR exists with review feedback: Go to step 7 (Handle PR Feedback).
State C — PR exists, CI failing: Go to step 7 (Handle PR Feedback — fix CI).
State D — PR exists, waiting for review: Nothing to do. Print "PR #N is waiting for review" and exit.
State E — No PR, progress comment exists with unchecked items: Go to step 5 (Implement Next Task).
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.
- 25d ago Changed · +2 tokens per session c4b90b532cd5
- 2mo ago First seen · 259 lines · 74 tokens per session scan A d08b491e7fb9
implementation-agent is a skill published in the GitHub repository band-app/band (5 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 2,006 once invoked, about $0.0003 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
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 zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…