f5-implement

A command for implementing features and fixing software bugs, with records that connect the work to specific issues.

In plain words
What is it for?
Use it to build features, fix bugs by ID or description, list or filter bugs, mark fixes complete, and verify them.
Why use it?
It keeps feature work and bug fixes in one workflow, including steps for listing, completing, and rechecking bugs. TDD, or test-driven development, means writing tests as part of the development process.

Command

Part of the f5-core plugin — 46 commands, 10 agents shipped together

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/fujigo-software/f5-framework-claude/f5-implement
Clone the repo
git clone --depth 1 https://github.com/Fujigo-Software/f5-framework-claude

Or install f5-core, the plugin that ships this one along with the rest of its 46 commands, 10 agents.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 9,549 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.00008 $0.09549
Opus 5 $0.00004 $0.04775
Sonnet 5 $0.00002 $0.01910
Haiku 4.5 $0.00001 $0.00955

Measured 3d ago against content hash 5e1080d591e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

f5-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 3d 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.

plugins/f5-core/commands/f5-implement.md · 1,468 lines

How it starts

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

/f5-implement - Unified Implementation Command

Consolidated command that replaces:

  • /f5-fix/f5-implement fix

Implement features and fix bugs with high quality, TDD support, and best practices.

ARGUMENTS

$ARGUMENTS

MODE DETECTION

Pattern Mode Description
fix <bug-id|desc> FIX Bug fix workflow
fix list FIX_LIST List all bugs
fix done <id> FIX_DONE Mark bug as fixed
fix verify <id> FIX_VERIFY Re-verify fix
<other> (default) IMPLEMENT Feature implementation

MODE: FIX (from /f5-fix)

/f5-implement fix <bug-id|description>

Structured workflow for fixing issues with traceability.

Action Description
<bug-id> Fix specific bug by ID
"<description>" Fix by description (creates new bug)
list List all bugs
done <bug-id> Mark bug as fixed
verify <bug-id> Re-verify after fix
list --status open Filter open bugs
list --severity high Filter by severity

Examples:

/f5-implement fix BUG-001
/f5-implement fix "Hero image wrong size"
/f5-implement fix list
/f5-implement fix done BUG-001
/f5-implement fix verify BUG-001

MODE: IMPLEMENT (Default)

Implement features with high quality and auto-agent support.

STEP 0: PRE-FLIGHT CHECKS

0.1 Load Integration Config

# Load command integration settings from .f5/config/command-integration.yaml
INTEGRATION_CONFIG=".f5/config/command-integration.yaml"
if [ -f "$INTEGRATION_CONFIG" ]; then
  COMMAND_CONFIG=$(cat "$INTEGRATION_CONFIG" | yq '.command_integration.f5-implement')
fi

0.2 Check MCP Prerequisites

📋 **MCP Pre-flight Check**

Required MCPs:
  - context7: [✅ Available / ⚠️ Not available]

Optional MCPs:
  - serena: [✅ Available / ○ Not configured]

{{#if MISSING_REQUIRED}}
⚠️ Missing required MCP: context7
Run: /f5-mcp install context7
Continuing with reduced capabilities...
{{/if}}

Read the full file on GitHub · 1,468 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.

  1. 3d ago First seen · 1,468 lines · 8 tokens per session scan A 5e1080d591e9

Subscribe to this mod's changes

f5-implement is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 9,549 once invoked, about $0.0000 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.