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/deploy)<a href="https://agentmods.dev/commands/robisson/build-like-amazon-agent-skills/deploy"><img src="https://agentmods.dev/badge/commands/robisson/build-like-amazon-agent-skills/deploy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/robisson/build-like-amazon-agent-skills/deploy"><img src="https://agentmods.dev/badge/commands/robisson/build-like-amazon-agent-skills/deploy.svg" alt="Reviewed on agentmods" width="80" 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.00849 |
| Opus 5.5 | $0.00000 | $0.00340 |
| Sonnet 5.5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
deploy 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 24d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy — Progressive Deployment
Path resolution: All
skills/,agents/, andpatterns/paths in this command are relative to the plugin root directory. Installed as a Claude Code plugin, that root is theBLA plugin root:line the plugin printed at session start; in a local install it is the working directory.
You are activating the deploy skill chain: feature-flag-lifecycle → progressive-deployment → pipeline-safety.
What to do
- Read skills at
skills/feature-flag-lifecycle/,skills/progressive-deployment/, andskills/pipeline-safety/. - Help the user plan and execute a safe deployment strategy.
Step 1: Feature Flag Lifecycle
If the approved design/spec uses feature flags, define the release lifecycle:
- Flag starts with safe default OFF.
- OFF behavior preserves existing behavior or graceful fallback.
- Kill switch behavior is documented and works without deployment.
- Rollout stages, success metrics, guardrail metrics, and stop conditions are defined.
- Cleanup task exists for after 100% rollout and stabilization.
If no feature flag is used, state why progressive deployment alone is sufficient.
Step 2: Progressive Deployment
Define the rollout plan:
- Stage 1 — One-box: Deploy to a single host. Bake for 30+ minutes. Watch error rates.
- Stage 2 — Regional canary: 5-10% of traffic in one region. Monitor key metrics.
- Stage 3 — Regional full: Full traffic in one region. Compare against control region.
- Stage 4 — Global rollout: Expand region by region with bake time between each.
For each stage define:
- Duration (minimum bake time)
- Success criteria (metrics that must stay green)
- Rollback trigger (automatic and manual conditions, including feature flag OFF when applicable)
- Approval gates (who approves promotion to next stage)
Step 3: Pipeline Safety
Load agents/ops-bar-raiser.md and review the deployment plan through the operations bar raiser lens.
Ensure the deployment pipeline enforces:
- Automated testing gate: Unit, integration, and contract tests pass.
- Static analysis gate: No new critical/high findings.
- Deployment hygiene: Infrastructure-as-code, no manual changes.
- Rollback capability: One-click rollback to previous known-good version.
- Alarm integration: Pipeline halts if production alarms fire during bake.
- Change management: Deployment windows, freeze periods, emergency procedures.
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.
- 24d ago Changed 643a943ec4bc
- 1mo ago Changed · +11 lines 4daef12516ad
- 2mo ago First seen · 57 lines · 0 tokens per session scan A dde794b58f83
deploy is a command published in the GitHub repository robisson/build-like-amazon-agent-skills (16 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 849 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
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
vios-release-note
Generate a complete VIOS multi-arch release note for a given build drop version. Fetches container images from GitLab compose.env, GitLab commit titles since the previous release tag, Jira VST tickets, NVBugs entries, Slack channel evidence, and Outlook email evidence, then renders and saves a formatted release note.
ci
Run CI validation, create PRs, and merge on green.
generate-changelog
Generate a changelog from git history, grouping commits by type and version.
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.