What is implement-approved-slice?

A controlled implementation workflow for one approved slice of an engineering task. A slice is a small, defined part of the work; the command makes the changes and records execution evidence, with an optional TDD mode that writes a failing test first.

Use it to implement a single approved feature or fix, optionally following TDD, or test-driven development.

It keeps implementation limited to agreed scope and leaves a reviewable record of what happened.

implement-approved-slice — Command for Claude Code by Mozurok

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.

Clone the repo

git clone --depth 1 https://github.com/Mozurok/fhorja.dev

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mozurok/fhorja.dev/implement-approved-slice/github.svg)](https://agentmods.dev/commands/mozurok/fhorja.dev/implement-approved-slice)

Your own site

<a href="https://agentmods.dev/commands/mozurok/fhorja.dev/implement-approved-slice"><img src="https://agentmods.dev/badge/commands/mozurok/fhorja.dev/implement-approved-slice/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mozurok/fhorja.dev/implement-approved-slice"><img src="https://agentmods.dev/badge/commands/mozurok/fhorja.dev/implement-approved-slice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 103 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 7,629 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00103	$0.07629
Opus 5.5	$0.00041	$0.03052
Sonnet 5.5	$0.00021	$0.01526
Haiku 4.5	$0.00010	$0.00763

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

Security

Grade A, and why

implement-approved-slice 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 10d 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.

commands/implement-approved-slice.md · 169 lines

How it starts

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

implement-approved-slice

Act as a senior engineer implementing a narrowly approved slice for the active engineering task.

Goal: Implement only the approved slice with minimal, explicit, review-friendly changes, then persist the execution result as reviewable execution notes (no rewrite without material change).

Mandatory context bootstrap (before any output):

Read these sections in WORKFLOW_OPERATING_SYSTEM.md first:
- ## LLM execution contract
- ## Editor mode policy (mode definitions only; the tool mapping table is lazy-loaded in wos/editor-mode-mappings.md and needed only for non-Claude-Code tools)
- ## Global output contract (including Adaptive handoff and Mode selection rule)
- ## Cross-cutting workflow guardrails
Bootstrap tiers: the light-weight commands (branch-commit, what-next, where-we-at, slice-closure, compact-task-memory) plus the high-frequency implement-approved-slice and sync-task-state (v3 wave1 item D) read the four sections above with two subsections of ## Cross-cutting workflow guardrails skipped: ### External web access (centralized) and ### Sequencing heuristics (by phase). Everything else is read at every tier, including ### Proposal vs approved persistence and ### Substrate peer ownership (per ADR-0034), since all seven write substrate sections and reason about PROPOSED (state-reconcile stays on the full tier for cross-artifact judgment). The full tier is measured at 12109 tokens, the four always-read sections combined; the two skipped subsections are 1,034 of those (measured 2026-09-28), so the reduced tier is about 11,074. The leaf-reviewer tier (verify-against-rubric, ADR-0226) reads only ## Global output contract, measured at 5215 tokens, plus its rubric.
Session bootstrap reuse (skip-if-unchanged; v3 wave1 item D): WHEN this conversation already read the bootstrap sections in an earlier turn still VISIBLE in the context window AND WORKFLOW_OPERATING_SYSTEM.md has not changed since, the command MAY skip the re-read and cite the earlier one, emitting one Command transcript line: Bootstrap: reusing turn <N> read, WOS unchanged. Scoped exception to the context-budget re-fetch rule (wos/context-budget.md, "The re-fetch rule"), because these sections are one large, static, byte-identical read repeated every turn; every other tool result still re-fetches. VISIBLE means the section text itself is still present and quotable now, not merely that a record of the earlier read exists: a harness that clears a tool result while the record survives (ADR-0114) has not satisfied VISIBLE, and self-declared memory after a compaction never qualifies. A stateless-per-turn harness is excluded. The transcript line is mandatory; a silent skip is invalid output.
Resolving the spec and wos/<topic>.md: canonical repository FIRST. Otherwise use active-adapter docs: ~/.claude/workflow-docs (CLAUDE_WORKFLOW_DOCS_DIR), ~/.cursor/workflow-docs (WORKFLOW_DOCS_DIR; project .cursor/workflow-docs on project installs), ~/.codex/workflow-docs (CODEX_WORKFLOW_DOCS_DIR), or <kimi-home>/workflow-docs (KIMI_WORKFLOW_DOCS_DIR). Nonempty overrides win. Kimi home: KIMI_CODE_HOME, else existing ~/.kimi-code, else existing ~/.kimi, default ~/.kimi-code. Use one root for both paths; try other adapters if absent or unknown. Report resolved root, fallback to other adapters, or missing mandatory context in ### Command transcript. Installed snapshots refresh and prune retired topics only on sync.
Read additional sections only when relevant to this command's role.
Align all routing recommendations and next-command suggestions with the current command set.
Official next-command names only: recommendations, including Run now, use registered names from commands/<name>.md or commands/<name>/SKILL.md; installed mode uses the available Fhorja command or skill inventory. No invented aliases. Run now: none with Mode: N/A ends only if no honest next step exists, defined under ### Official command names (routing integrity) (ADR-0126). Required inputs:
active task folder path
TASK_STATE.md
SOURCE_OF_TRUTH.md
DECISIONS.md
IMPLEMENTATION_PLAN.md
TEST_STRATEGY.md, if available
relevant real codebase context
current approved slice definition
last completed step from TASK_STATE.md (command + summary)
optional: --tdd to run this slice test-first (ADR-0063; also per slice via Test-first: yes in the plan)

Read the full file on GitHub · 169 lines

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.

10d ago Changed · -23 lines · -58 tokens per session 407318367b77
13d ago Changed · +2 lines 1a1328264d15
20d ago Changed · -1 lines 97c1f8410281
21d ago Changed · -10 lines · -41 tokens per session 7cb338fb08cc
1mo ago First seen · 201 lines · 202 tokens per session scan A 14630d75c421

Subscribe to this mod's changes

implement-approved-slice is a command published in the GitHub repository Mozurok/fhorja.dev (10 stars, last pushed 11d ago), licensed MIT. It adds 103 tokens to every session and 7,629 once invoked, about $0.0004 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-09-03.

Claude Code Project management TDD Testing agent-skills ai-coding cursor developer-tools spec-driven-development

implement-approved-slice

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

implement-approved-slice

What this file has done since we first saw it

Other commands, from other repositories

implement

spec-impl

kiro-spec-impl

execute-work-packet

execute

forge