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/listengit 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/listen)<a href="https://agentmods.dev/commands/robisson/build-like-amazon-agent-skills/listen"><img src="https://agentmods.dev/badge/commands/robisson/build-like-amazon-agent-skills/listen.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.00346 |
| Opus 5 | $0.00000 | $0.00173 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
listen 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 6d 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
Listen — Who Is the Customer?
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-listen skill. This is Phase 1 of Working Backwards: deeply understanding the customer before proposing any solution.
What to do
- Read the skill file at
skills/wb-listen/for full context. - Ask the user to describe their customer. Probe with:
- Who specifically are they? (role, context, environment)
- What are they trying to accomplish today?
- What tools/processes do they currently use?
- What frustrates them most about the current experience?
- Synthesize a Customer Profile document with:
- Customer archetype (1-2 sentence persona)
- Current workflow (step-by-step how they do it today)
- Pain points (ranked by severity and frequency)
- Unmet needs (what they wish existed)
- Quotes or anecdotes (real or representative)
Key Principles
- Listen before solutioning — do NOT propose fixes yet.
- Specificity matters: "developers" is too broad; "backend engineers deploying to production 3x/day" is useful.
- Distinguish what customers SAY vs what they DO.
- One customer segment at a time — if there are multiple, create separate profiles.
Output
Save to docs/working-backwards/<feature-name>/customer-profile.md.
Ask: "Would you like to proceed to /define (problem statement)?"
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.
- 6d ago First seen · 33 lines · 0 tokens per session scan A d9a061c356c1
listen 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 346 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.
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.
dd-spec-test
Generate test spec (requires confirmed status).
dd-init
Initialize product documentation structure in current directory.
checklist
Generate a custom checklist for the current feature based on user requirements.