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.
npx agentmods add commands/ecro/embedeval/wrapupgit clone --depth 1 https://github.com/Ecro/embedevalWhat 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 | $0.00000 | $0.01082 |
| Opus 5 | $0.00000 | $0.00541 |
| Sonnet 5 | $0.00000 | $0.00216 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
wrapup 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 yesterday.
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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wrapup — Finalize and commit
Final validation, docs sync, and commit. Step 5 of the embedeval 5-stage workflow. Reports to screen only — no WRAPUP/LEARNING document.
Communication
- Direct, evidence-based.
- Never commit on a red gate. Never push without explicit user confirmation.
- Report what actually happened — don't paper over a skipped step.
Usage
/wrapup [task-slug]
Slug is optional — used in commit message if provided; inferred from the PLAN referenced by the diff otherwise.
Context
- Repo:
/home/noel/embedeval - PLAN (if slug given):
plans/PLAN-<slug>.md - Pre-commit hook at
.githooks/pre-commitmirrors the ruff subset. Activate per clone:git config core.hooksPath .githooks. Never skip with--no-verify. - Quality gates — MANDATORY, all must pass:
uv run ruff format --check src/uv run ruff check src/uv run mypy src/uv run pytest tests/ -v --tb=short
- Doc auto-sync — MANDATORY when
cases/,src/, ortests/changed:uv run python scripts/sync_docs.py
Steps
-
Preflight
git status --short— show uncommitted changes.- Confirm branch. Warn if on
maindirectly without the agent-branch convention:agent/<slug>/<YYYY-MM-DD>.
-
Full quality gate
- Run all four gates sequentially. Stop on first failure; report exact error and exit. Do not commit.
-
Doc auto-sync
- If the diff (staged + unstaged + last commit vs HEAD~1) touches
cases/,src/, ortests/:- Run
uv run python scripts/sync_docs.py. - If
README.mdordocs/METHODOLOGY.mdchanged, stage them.
- Run
- If the script prints "already up to date", no action.
- If the diff (staged + unstaged + last commit vs HEAD~1) touches
-
Self-review diff
- Print
git diff --statfor staged + unstaged. - Sanity-check against CLAUDE.md "Quality Gates" #1 (API contracts, redundant calls, edge cases).
- Ask user to confirm before committing.
- Print
-
Refresh test tracker (if
cases/changed)if git diff --name-only HEAD~1 -- cases/ | grep -q .; then uv run embedeval refresh-tracker --cases cases/ --results results/ fi
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.
- yesterday First seen · 124 lines · 0 tokens per session scan A 132712edb629
wrapup is a command published in the GitHub repository Ecro/embedeval (11 stars, last pushed 26d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,082 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.