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/niels-emmer/myace/evaluategit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/evaluate)<a href="https://agentmods.dev/commands/niels-emmer/myace/evaluate"><img src="https://agentmods.dev/badge/commands/niels-emmer/myace/evaluate.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00185 |
| Opus 5 | $0.00010 | $0.00093 |
| Sonnet 5 | $0.00004 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
evaluate 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 today.
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.
What it actually says
- Run the model against the held-out test set and log all metrics.
- Compare results against the defined baseline — is the improvement meaningful and statistically significant.
- Run a data leakage scan on the full pipeline (features → split → training).
- Evaluate on slices/subgroups to identify failure pockets.
- Document known failure modes: conditions where the model performs poorly, edge cases it doesn't handle.
- Update the model registry entry with evaluation results and artifact location.
- Flag any gap between training metrics and expected production performance.
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.
- today First seen · 14 lines · 20 tokens per session scan A 6ed7e123b172
evaluate is a command published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 185 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
brainstorm
已弃用 - 请改用 superpowers:brainstorming 技能.
handoff
Force a session catchup or a memory promotion outside the hook lifecycle. Default is catchup (read-only); promote is HITL gated.
fix
Apply a single safe quick win from DESIGN.md.critique.md. HITL gated. Re-lints DESIGN.md after every edit; reverts if lint regresses.
compose
One-shot wiring check for MDDesign. Verifies planning-with-files, DESIGN.md, code-memory-router, and Google linter are all reachable. Surfaces any missing piece with a one-line fix-it. Read-only.
dev-implement
Before executing this command, CONFIRM these files exist and are readable.
orchestrator-fix
Before executing this command, CONFIRM these files exist and are readable.