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/robisson/build-like-amazon-agent-skills/test-ideagit clone --depth 1 https://github.com/robisson/build-like-amazon-agent-skillsWrote 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/robisson/build-like-amazon-agent-skills/test-idea)<a href="https://agentmods.dev/commands/robisson/build-like-amazon-agent-skills/test-idea"><img src="https://agentmods.dev/badge/commands/robisson/build-like-amazon-agent-skills/test-idea.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.1 | $0.00000 | $0.00385 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
test-idea 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 5d 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.
What it actually says
Test Idea — How Will We Measure Success?
Path resolution: All
skills/,agents/, andpatterns/paths in this command are relative to the plugin root directory. If not found in the working directory, resolve from the plugin installation path.
You are activating the wb-test-and-iterate skill. This is Phase 5 of Working Backwards: defining how to validate the idea and measure its impact.
What to do
- Read the skill file at
skills/wb-test-and-iterate/for full context. - Review the PR/FAQ and solution sketch from previous phases.
- Help the user define a validation and metrics plan:
- What are the key assumptions that must be true for this to succeed?
- How can we test each assumption cheaply and quickly?
- What does the MVP look like? (minimum to learn, not minimum to ship)
- What metrics prove we're solving the problem?
- Write a Success Metrics document with:
- Input metrics (what we control: adoption, usage, features shipped)
- Output metrics (what we hope to move: satisfaction, time saved, errors reduced)
- Guardrail metrics (what must NOT get worse)
- Target values and measurement timeline
- Kill criteria (when do we stop if it's not working?)
Key Principles
- Measure outcomes, not outputs — "customer success" not "features shipped."
- Every metric needs a baseline, target, and deadline.
- Prefer leading indicators over lagging ones.
- Design experiments that can fail — unfalsifiable tests teach nothing.
- Two-pizza team should own the metrics end-to-end.
Output
Save to docs/working-backwards/<feature-name>/success-metrics.md.
Ask: "Working Backwards is complete. Ready to /design the technical solution?"
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.
- 5d ago First seen · 35 lines · 0 tokens per session scan A fbcde1f05eea
test-idea is a command published in the GitHub repository robisson/build-like-amazon-agent-skills (14 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 385 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-30.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
wp-set-attributes
The WP SET ATTRIBUTES command allows you to set the value of any attribute in a range, element, document. This command gives you access to any kind of 4D Write Pro internal attribute: character, paragraph, document, table, or image.
verify
Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.