A command for carrying out an approved implementation plan and running checks such as formatting, linting, type checks, tests, and builds.

Implementing planned work, checking errors, and validating the result manually and automatically.

It provides a repeatable implementation and quality-check routine instead of stopping after code changes.

How hudrazine/claude-code-memory-bank configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to hudrazine/claude-code-memory-bank. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/hudrazine/claude-code-memory-bank/main/.claude/commands/workflow/execute.md

Clone the repo

git clone --depth 1 https://github.com/hudrazine/claude-code-memory-bank

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/hudrazine/claude-code-memory-bank/execute/github.svg)](https://agentmods.dev/commands/hudrazine/claude-code-memory-bank/execute)

Your own site

<a href="https://agentmods.dev/commands/hudrazine/claude-code-memory-bank/execute"><img src="https://agentmods.dev/badge/commands/hudrazine/claude-code-memory-bank/execute/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/hudrazine/claude-code-memory-bank/execute"><img src="https://agentmods.dev/badge/commands/hudrazine/claude-code-memory-bank/execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 766 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.00006	$0.00766
Opus 5.5	$0.00002	$0.00306
Sonnet 5.5	$0.00001	$0.00153
Haiku 4.5	$0.00001	$0.00077

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

Security

Grade A, and why

execute 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 2mo 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.

.claude/commands/workflow/execute.md · 110 lines

How it starts

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

Implementation & Quality Assurance

Task

Think carefully about implementation details and execute the planned solution with focus on quality.

$ARGUMENTS

Implementation Process

Setup & Preparation

Review the approved plan or task requirements
Verify working on correct branch with no conflicting changes
For complex implementations, consider using TodoWrite to track progress

Code Implementation

Follow project patterns:

Adhere to existing coding conventions and architectural patterns
Implement incrementally with validation between significant changes
Use MultiEdit for cohesive multi-file modifications
Maintain clean, readable code with appropriate error handling

Quality during development:

Test functionality after each component is implemented
Check for compile/syntax/type errors regularly
Ensure edge cases are properly handled

Quality Assurance

Automated Checks

Run all relevant project quality tools:

Code formatting and linting
Type checking and static analysis
Unit and integration tests
Build verification

Manual Validation

Test implemented features thoroughly
Verify error messages are user-friendly
Ensure no debug code or temporary TODOs remain
Confirm implementation matches requirements

Completion Review

Final Checklist

All changes follow project patterns ✓
Quality checks pass ✓
Implementation matches plan ✓
No regressions introduced ✓

Summary Report

Changes: List files modified and key implementations Quality Status: Report results of all checks Next Steps: Any follow-up work or discovered improvements

Guidelines

Prioritize correctness and quality over speed
Ask for clarification if requirements are ambiguous
Report any issues discovered during implementation
Keep changes focused on the approved scope
If blocked, document the issue clearly and suggest solutions

Feedback Loop Handling

During implementation, if you encounter:

Requirements Uncertainty

Symptom: Unclear specifications, ambiguous edge cases, missing context
Action: Pause implementation → Document findings → /workflow:understand for clarification
Example: "The API specification doesn't define error response format"

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

2mo ago First seen · 110 lines · 6 tokens per session scan A f8cb282dcb59

Subscribe to this mod's changes

execute is a command published in the GitHub repository hudrazine/claude-code-memory-bank (42 stars, last pushed 1y ago), licensed Unlicense. It adds 6 tokens to every session and 766 once invoked, about $0.0000 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-08-30.

Planning

execute next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
executehudrazine/claude-code-memory-bank	Command	42	1y ago	Unlicense	A	6	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

claude-code-memory-bank: Command for Claude Code