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/specgit 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/spec)<a href="https://agentmods.dev/commands/robisson/build-like-amazon-agent-skills/spec"><img src="https://agentmods.dev/badge/commands/robisson/build-like-amazon-agent-skills/spec.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.00000 | $0.01569 |
| Opus 5 | $0.00000 | $0.00785 |
| Sonnet 5 | $0.00000 | $0.00314 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
spec 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 4d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec — Create a New Implementation Spec
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.
This command creates a single new spec (vertical slice of value) when the design phase is already complete. Use it to incrementally add features, endpoints, or capabilities without re-running the full /design flow.
Step 0: State Detection + Proportionality Check
Before creating a spec, detect the project state and classify the requested change. The user should not have to think about which path is right — the agent decides, and asks only when there is genuine ambiguity.
-
Read repo state:
- Does
docs/design/<feature-or-service>/design-doc.mdexist (greenfield with full flow)? - Does
docs/design/contain a reverse-engineered Design Doc (banner says "REVERSE-ENGINEERED" — produced by/onboard)? - Does the project have significant code, IaC, CI but no BLA artifacts (brownfield, no onboarding done)?
- Are there existing specs in
specs/that already cover this slice?
- Does
-
Classify the requested change using the ladder in
skills/using-amazon-skills/SKILL.md: Trivial / Small / Medium / Large. -
Decide the path:
State Change size Path Design Doc exists (canonical or reverse-engineered) Medium / Large Proceed with full spec creation below. Design Doc exists Trivial / Small The spec is overkill for this size. Recommend going direct via /buildinstead. UseAskUserQuestionto confirm before creating a heavy spec.No Design Doc, brownfield project Medium / Large Use AskUserQuestionto offer: [A] Run/onboardfirst to reverse-engineer the project (recommended for medium+), then create the spec; [B] Create a lightweight spec anchored on the existing code without a Design Doc; [C] Run full/designfrom scratch. Pick one before proceeding.No Design Doc, brownfield project Trivial / Small Recommend skipping spec creation; go direct via /build. Confirm with the user.No Design Doc, greenfield project any Recommend /designfirst. Spec creation needs an anchor.
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.
- 4d ago First seen · 107 lines · 0 tokens per session scan A fa762e209df8
spec 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,569 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
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
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.