Borrowing it
Nothing to install: this file belongs to Ecro/embedeval. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Ecro/embedeval/main/.claude/commands/execute.mdgit clone --depth 1 https://github.com/Ecro/embedevalWrote 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.
[](https://agentmods.dev/commands/ecro/embedeval/execute)<a href="https://agentmods.dev/commands/ecro/embedeval/execute"><img src="https://agentmods.dev/badge/commands/ecro/embedeval/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.
<a href="https://agentmods.dev/commands/ecro/embedeval/execute"><img src="https://agentmods.dev/badge/commands/ecro/embedeval/execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00837 |
| Opus 5.5 | $0.00000 | $0.00335 |
| Sonnet 5.5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/execute — Implement the PLAN
Implement the PLAN with continuous verification. Step 3 of the embedeval 5-stage workflow. Reports to screen only — no SESSION document.
Communication
- Direct, evidence-based, no preamble.
- Never fabricate progress. Say when a step fails.
- Lead with blockers before claiming success.
Usage
/execute <task-slug>
Requires plans/PLAN-<slug>.md produced by /myplan.
Context
- Repo:
/home/noel/embedeval - PLAN source:
plans/PLAN-<slug>.md - Quality gates (run between phases and before handoff):
uv run ruff format --check src/uv run ruff check src/uv run mypy src/uv run pytest tests/
- Doc auto-sync (mandatory if
cases//src//tests/changed before commit):uv run python scripts/sync_docs.py - Pre-commit hook at
.githooks/pre-commitruns the ruff subset; never bypass with--no-verify.
Steps
-
Load PLAN — Read
plans/PLAN-<slug>.md. If missing, error: user must run/myplan <slug>first. -
Confirm scope — echo TL;DR and success criteria. Stop if anything is still ambiguous — ask, don't guess.
-
Phase-by-phase implementation — for each phase in the PLAN: a. State the phase goal in one line. b. Apply code changes with Edit/Write — never blind-append. Read before edit. c. Run the relevant quality-gate subset (minimum:
ruff check src/and the affectedpytest tests/<module>). d. Report outcome: files changed, tests added, gate result. e. If blocked ≥ 2 attempts: stop and escalate (ask user, or delegate to a specialized agent). Do not push around a block with--no-verify, weakened tests, or skipped steps. -
Full quality gate before handoff — run all four gates and
sync_docs.pyif applicable. Fail fast; don't hide a red gate behind a summary. -
Update PLAN checkboxes — tick implementation-phase items that are now done. (This is the only file modification
/executemakes outsidesrc/,tests/, andcases/.)
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 · 100 lines · 0 tokens per session scan A 53719d68a2d7
execute is a command published in the GitHub repository Ecro/embedeval (13 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 837 tokens. 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.