implement-task

A workflow for picking up a Binder task, where Binder is the project's task-tracking system for bugs, questions, designs, and implementation work.

In plain words
What is it for?
It is for reading a task, checking its status, selecting active or pending work, and then discussing, designing, testing, or implementing the requested change.
Why use it?
It prevents work from starting on tasks that are unfinished, cancelled, or already complete, and helps choose the right investigation or design guide.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/mpazik/binder/implement-task
Any agent
npx skills add mpazik/Binder --skill implement-task
Clone the repo
git clone --depth 1 https://github.com/mpazik/Binder

Made for: Claude Code, Codex.

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 633 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00051 $0.00633
Opus 5 $0.00026 $0.00316
Sonnet 5 $0.00010 $0.00127
Haiku 4.5 $0.00005 $0.00063

Measured yesterday against content hash c9b66b7b4ff6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement-task 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 yesterday.

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.

examples/workflow/skills/implement-task/SKILL.md · 63 lines

How it starts

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

Work on a task. Provide a task key, or omit to pick from the lists below.

$ARGUMENTS

If a task key was given above, read it with binder read <key> --format yaml. If the key doesn't exist, tell the user and stop. Otherwise, pick from the lists below and then read it.

Check the task's status:

  • draft — needs refinement first, not ready to work on. Tell the user.
  • complete or cancelled — nothing to do. Tell the user.
  • pending, active, paused — proceed.

Active Tasks

!binder search type=Task status=active -f "key,title,taskType,size,priority,module" --format tsv

Pending Tasks

!binder search type=Task status=pending -f "key,title,taskType,size,priority,module" -o "!priority" --format tsv

Choosing a guide

After reading the task, decide which guide to load based on what it needs right now.

Condition Guide
fix task, rootCause empty guides/investigate.md — find root cause
requires or relatesTo links to a Problem record (check linked keys) guides/discuss.md — resolve open questions
specification empty, and task is medium+, refactor, or agent guides/design.md — produce a specification
fix/feat/refactor/test task that still needs tests guides/write-tests.md — write tests
None of the above apply guides/implement.md — implement

Multiple conditions can match. Start with the topmost one that applies, or follow the user's direction. Read the guide, then follow its instructions.

After completing a guide, re-read the task and check the table again. If another condition applies, load that guide next. If no conditions match, go to implement.

Updating multi-line fields

For single-value fields: binder update <key> field=value

For multi-line or rich text fields (rootCause, specification, details, etc.), use a transaction file:

- author: agent
  records:
    - $ref: <key>
      specification: |
        ## Approach
        ...

Read the full file on GitHub · 63 lines

Files

What ships with it

7 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. yesterday First seen · 63 lines · 51 tokens per session scan A c9b66b7b4ff6

Subscribe to this mod's changes

implement-task is a skill published in the GitHub repository mpazik/Binder (40 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 633 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-30.

Related

Other skills, from other repositories

engraphis-memory

Give the agent durable, scoped, explainable memory across sessions and repositories through the Engraphis MCP tools. Use when you learn a convention, decision, bug cause/fix, or user preference worth keeping; when prior context would help before you answer or act (to avoid re-asking or re-deriving); when asked "why is…

Coding-Dev-Tools/engraphis · 134 tokens

encyclopedia-writing

Encyclopedic neutral-reference writing craft — NPOV (attribute facts not opinions, due weight, neutral faction labels, verdict restraint), summary style and Coatrack avoidance, wikilink conventions (link density, first-mention, slug alias, abbreviation glossing). Use when writing or reviewing a neutral…

alfadur7/llm-wiki-newsroom · 95 tokens

guideline-writing

Guideline-authoring craft for instruction SoTs (.claude/ guides, CLAUDE.md, plan files) — operative rules vs recital, MUST/SHOULD/MAY force tiers, pruning, bloat control, blind review protocol, deliberation-narrative ban. Use when writing, editing, or reviewing an agent instruction file, policy, runbook, command SoT…

alfadur7/llm-wiki-newsroom · 99 tokens

journalism-writing

Journalism and argumentation writing craft — inverted pyramid, lede, nut graph, kicker, explainer framing, PAGE frames, Toulmin argument (claim/rebuttal/qualifier), Hegelian dialectic, BBC due impartiality. Use when writing or reviewing news/explainer pieces, landscape overviews, or issue analyses that fairly…

alfadur7/llm-wiki-newsroom · 95 tokens

scholarly-citation

Verifiable-attribution and citation-discipline craft — atomic claim decomposition, evidence grading (primary/analysis/forecast tiers), claimant attribution, citation typing (cites/references/contradicts/defines), source anchoring (Xanadu). Use when writing or reviewing a reference or synthesis page that attributes and…

alfadur7/llm-wiki-newsroom · 92 tokens

consulting-writing

Management-consulting writing craft — McKinsey SCR (Situation·Complication·Resolution), Minto Pyramid/MECE, BCG bold-bullet executive summary, so-what upfront, numeric precision, Forrester Landscape. Use when writing or reviewing an executive summary for decision-makers or a roll-up/landscape overview, or when a…

alfadur7/llm-wiki-newsroom · 91 tokens