implement-issue

implement-issue is a skill for Claude Code from scharissis/polako. It costs 0 tokens per session (15,977 once invoked), scanned A, original, MIT.

A workflow for taking a GitHub issue—the project's tracked task—from its initial plan through implementation and a pull request, a proposed code change for review. It can continue after clarification questions.

In plain words
What is it for?
Use it to implement a specific GitHub issue, handle clarification pauses, keep long waits active, and prepare the resulting branch and pull request.
Why use it?
It keeps issue work from being left unfinished when the agent needs answers or must wait for checks. It also makes sure required results are collected before the run ends.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents.

Part of the polako plugin — 5 skills shipped together

Good fit Use it to implement a specific GitHub issue, handle clarification pauses, keep long waits active, and prepare the resulting branch and pull request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/scharissis/polako/implement-issue
Install

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.

Any agent
npx skills add scharissis/polako --skill implement-issue
Clone the repo
git clone --depth 1 https://github.com/scharissis/polako

Made for: Claude Code.

Or install polako, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for implement-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/scharissis/polako/implement-issue/github.svg)](https://agentmods.dev/skills/scharissis/polako/implement-issue)
Your own site
<a href="https://agentmods.dev/skills/scharissis/polako/implement-issue"><img src="https://agentmods.dev/badge/skills/scharissis/polako/implement-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.

agentmods 80×15 button for implement-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/scharissis/polako/implement-issue"><img src="https://agentmods.dev/badge/skills/scharissis/polako/implement-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 15,977 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.15977
Opus 5.5 $0.00000 $0.06391
Sonnet 5.5 $0.00000 $0.03195
Haiku 4.5 $0.00000 $0.01598

Measured 22d ago against content hash 0064ad092c22, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement-issue scanned grade A with 1 finding 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 22d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

already sits inside this run's grant; none of it needs `curl`, `sleep`
skills/implement-issue/SKILL.md · 1,040 lines

How it starts

The opening of the file, as written. The whole thing — 1,040 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement GitHub issue #$issue

This run gets one turn

Ending your turn ends the process. There is no later turn to come back to and nothing that can wake you — not a Monitor, not a scheduled wake-up, not a background job you meant to poll, not a subagent whose result you never awaited. Whatever the worktree holds the moment you stop is all the run leaves behind: uncommitted edits, an unpushed branch, no PR. To the supervisor that is indistinguishable from a run that produced nothing, so a perfectly good issue gets parked. Interactively every one of those waits works, which is exactly why this needs saying.

So anything whose result you need is waited for inside this turn, however long it takes. Never end a turn intending to resume. A measurement worth taking is worth blocking on; one not worth blocking on should be dropped rather than deferred.

Waiting is not the same as going quiet, though. A supervisor kills and resumes a run that emits nothing for -stall — fifteen minutes by default — so a wait longer than that is polled from here, in repeated calls that keep the run visibly alive, rather than spent inside one call a watchdog cannot tell from a hang. Poll it slowly — a check every minute or two. Each check is a fresh turn that reloads the whole late-session context, so polling faster costs a lot and buys nothing. Backgrounding the slow thing is fine; what is not is the turn ending while it is still outstanding.

Polling is only for work still running when you look. A Skill call that hasn't returned yet needs none: the harness holds the turn until it returns, so a ListAgents or Bash: true heartbeat beside it is waste. But a return is not proof the work behind it is done, however finished its prose reads — the skill may still have subagents running in the background. So before trusting a Skill call's result, check ListAgents: nothing related still running means done; anything still running is backgrounded work, polled slowly as above. Phase 3 step 2c says how the review gate checkpoints what arrives while it waits.

Read the full file on GitHub · 1,040 lines

Files

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.

Changes

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.

  1. 22d ago Changed · +106 lines 0064ad092c22
  2. 24d ago Changed · -8 lines 60ea8a1977f3
  3. 26d ago Changed · +56 lines d5764af89e39
  4. 27d ago Changed · +241 lines 15d85493494d
  5. 28d ago Changed · +116 lines · -15 tokens per session a69848b230b3
  6. 1mo ago Changed · +162 lines 00b890d1aa5f
  7. 1mo ago First seen · 367 lines · 15 tokens per session scan A 24dbcbe1f9aa

Subscribe to this mod's changes

implement-issue is a skill published in the GitHub repository scharissis/polako (1 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 15,977 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.