amby.implement

A task-execution command for projects that organize work into tasks, stories, plans, and acceptance criteria.

In plain words
What is it for?
Use it to implement the next available task, add or adjust tests, update task and story status, and report the next unblocked task.
Why use it?
It keeps implementation aligned with planned requirements and dependencies, reducing the risk of starting blocked work or forgetting project updates.

Command for Claude Code

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 commands/ambystechcom/ambykit/amby.implement
Clone the repo
git clone --depth 1 https://github.com/ambystechcom/AmbyKit

Made for: Claude Code.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 376 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.00016 $0.00376
Opus 5 $0.00008 $0.00188
Sonnet 5 $0.00003 $0.00075
Haiku 4.5 $0.00002 $0.00038

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

Security

Grade A, and why

amby.implement 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.

.claude/commands/amby.implement.md · 22 lines

What it actually says

Act as the Developer in @.amby/roles/developer.md and say so in your first line. If $ARGUMENTS contains --as <id>, use @.amby/roles/<id>.md instead; if that file is missing, stop and list the files in .amby/roles/.

Implement work for $ARGUMENTS (default: the next unblocked task in priority order).

  1. From tasks.md, pick the target task(s). Respect the Foundational-before-features gate and the story dependency graph — never start a task whose story is blocked-by unfinished work.
  2. Load only the slice you need: the task line, the relevant plan.md section, and the specific files named. Don't read the whole spec tree (token-frugal).
  3. Implement to satisfy the mapped FR-###/acceptance criteria and the constitution. Add/adjust tests for the acceptance criteria.
  4. Patch in place: flip the completed task's checkbox to - [x] in tasks.md; when all of a story's tasks are done, set that story's status: done in spec.md (or in-progress while partway). Don't rewrite untouched sections.
  5. Report what you did and the next unblocked task. Stop at a story checkpoint for review.
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 · 22 lines · 16 tokens per session scan A c2a4bb580bae

Subscribe to this mod's changes

amby.implement is a command published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 376 once invoked, about $0.0001 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.