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.
git 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/onboard)<a href="https://agentmods.dev/commands/robisson/build-like-amazon-agent-skills/onboard"><img src="https://agentmods.dev/badge/commands/robisson/build-like-amazon-agent-skills/onboard.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.01851 |
| Opus 5 | $0.00000 | $0.00925 |
| Sonnet 5 | $0.00000 | $0.00370 |
| Haiku 4.5 | $0.00000 | $0.00185 |
Grade A, and why
onboard 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 7d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard — Reverse-Engineer an Existing Project
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.
/onboard activates the brownfield-discovery skill. It runs once per project (or when the project drifts significantly) and produces anchoring artifacts derived from the real code, IaC, and observability.
/onboard has three paths, picked by the user at the start. The agent classifies and asks; the user picks an outcome, not a process step.
| Path | Outcome | Time |
|---|---|---|
| A — Anchor only (default, recommended) | Design Doc + API contracts + Threat Model from existing code. No customer/PR/FAQ. | ~15–30min |
| B — Validate the why | Path A + reverse-engineered PR/FAQ + hard questions from doc-bar-raiser where the code can't tell us why |
~30–45min |
| C — Forward WB + Gap Analysis | Full canonical /wb from scratch (5 stages with gates, agent reading existing code) + Path A + gap-analysis.md |
~1–2h |
The output anchors all subsequent /spec and /build invocations — instead of re-discovering the project on every change, the agent reads the persisted artifacts.
When to Use
- The project already has significant code, IaC, CI, and possibly observability — but no Build Like Amazon artifacts (
docs/design/,docs/working-backwards/) - A medium or large change is coming, and anchoring the agent on the real state of the project will pay back many times
- The user explicitly invokes
/onboard - The project has drifted significantly from the prior reverse-engineered baseline (architecture change, major refactor, new pattern adopted)
- The user wants to validate that what's been built actually serves a real customer problem (Path B)
- The project is pivoting / re-strategizing and the user wants to re-derive the WB from scratch and see the gap (Path C)
When NOT to Use
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.
- 7d ago First seen · 120 lines · 0 tokens per session scan A 33f11938ec7f
onboard 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 1,851 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.