A handoff command for implementing one tracked task: it reads the task, checks prerequisites, makes the code changes, runs local checks, and records evidence.

Use it to carry out one TASK record and pass the implementation results to separate verification or scheduling steps.

It gives a single task a consistent implementation and verification routine without deciding whether the task is finally closed.

execute — Command for Claude Code by mrvladd-d/memobank

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/mrvladd-d/memobank

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/mrvladd-d/memobank/execute/github.svg)](https://agentmods.dev/commands/mrvladd-d/memobank/execute)

Your own site

<a href="https://agentmods.dev/commands/mrvladd-d/memobank/execute"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/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/mrvladd-d/memobank/execute"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,038 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.00029	$0.02038
Opus 5.5	$0.00012	$0.00815
Sonnet 5.5	$0.00006	$0.00408
Haiku 4.5	$0.00003	$0.00204

Measured 1mo ago against content hash 5f3a02ec3418, 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 1mo 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.

skills/_shared/references/commands/execute.md · 182 lines

How it starts

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

/execute - Execute One TASK

Status Transition Modes

Status transitions have two modes.

Scheduler mode:

/autopilot and /autonomous own task status transitions.
Scheduler decides closure/failure/blocking eligibility.
/execute returns scoped implementation handoff; it does not close tasks.
/verify gives functional verdict/evidence; in scheduler mode it does not close/fail/block/promote.
/red-verify gives semantic verdict for T2/T3; in scheduler mode it does not close/fail/block/promote.
Scheduler must write the closure/failure/blocking decision, final task status, and evidence links to the authoritative indexed .memory-bank/tasks/TASK-*.task.json record before /mb-sync.
/mb-sync records/reconciles already-written task state. It does not decide closure/failure/blocking/promotion and must not sync a decision that exists only in scheduler context.
T0/T1 scheduler closure may use compact evidence / functional PASS according to tier policy.
T2/T3 scheduler closure requires VERDICT: PASS plus SEMANTIC_VERDICT: semantic-pass before scheduler marks done.
T3 scheduler closure also requires exact markers HUMAN_CHECKPOINT: done and ROLLBACK_RECOVERY_NOTE: present.

Manual mode:

Expected T0/T1 simple flow: /execute -> /verify for one TASK.
Manual closure is allowed only when an explicit closure owner exists.
explicit standalone owner means either the user directly asked the current top-level agent to close the task, or the top-level agent/orchestrator explicitly runs a manual workflow for one TASK and records that it owns closure. Subagents/worker prompts do not silently become closure owners.
/verify PASS may mark T0 / T1 status: done only when explicit closure ownership is present and completed evidence has been written to the task record verify field and the compact/full protocol required by tier.
If explicit closure owner is absent, /verify records VERDICT: PASS, evidence, and a closure recommendation, leaves status unchanged, and tells the scheduler/owner to close.
T2 / T3 manual closure requires /verify PASS plus /red-verify SEMANTIC_VERDICT: semantic-pass before status: done or /mb-sync; if semantic-pass is absent, leave closure pending or blocked, not done.
semantic-concern in manual mode means do not trust the existing done state without human review / follow-up.
Do not mix scheduler mode and manual mode inside one task run.
No persisted mode field is used.

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

1mo ago First seen · 182 lines · 0 tokens per session scan A 5f3a02ec3418

Subscribe to this mod's changes

execute is a command published in the GitHub repository mrvladd-d/memobank (56 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 2,038 once invoked, about $0.0001 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.

Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

fest-show

Show festival progression (in-progress tasks, roadmap, and dependency view).

Obedience-Corp/festival · 17 tokens

add-note

Add an internal or external note to a ConnectWise PSA ticket.

WYRE-AI/msp-claude-plugins · 12 tokens

dispatcher

Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…

Kanevry/session-orchestrator · 185 tokens

sync-linear

Sync current work with Linear ticket status.

bybren-llc/safe-agentic-workflow · 0 tokens

workpm

A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.

Dannykkh/skill-olympus · 31 tokens