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 skills add robisson/build-like-amazon-agent-skills --skill pipeline-safetygit 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/skills/robisson/build-like-amazon-agent-skills/pipeline-safety)<a href="https://agentmods.dev/skills/robisson/build-like-amazon-agent-skills/pipeline-safety"><img src="https://agentmods.dev/badge/skills/robisson/build-like-amazon-agent-skills/pipeline-safety/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/skills/robisson/build-like-amazon-agent-skills/pipeline-safety"><img src="https://agentmods.dev/badge/skills/robisson/build-like-amazon-agent-skills/pipeline-safety.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.00022 | $0.01503 |
| Opus 5 | $0.00011 | $0.00751 |
| Sonnet 5 | $0.00004 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00150 |
Grade A, and why
Pipeline Safety 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 11d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Safety
Overview
A safe pipeline is one that makes it harder to deploy bad code than good code. It enforces automated quality gates at every stage, blocks deployments when alarms are firing, provides one-click rollback, and creates an audit trail of every production change. The pipeline is not a convenience tool—it is a safety system that protects customers.
When to Use
- Setting up a new service's CI/CD pipeline
- Adding safety gates to an existing pipeline
- Reviewing pipeline configuration for operational readiness
- After any incident caused by a deployment that should have been caught
- When a team is deploying less frequently due to fear of breaking things (symptom of insufficient safety)
Amazon Context
Amazon's deployment philosophy: the pipeline should be the safest, fastest path to production. If developers feel tempted to bypass the pipeline, the pipeline is broken—either too slow or too fragile. A good pipeline deploys hundreds of times per day across a large organization while catching the handful of changes that would have caused customer impact. The investment in pipeline safety is what enables high deployment velocity.
The Process
Pre-Commit Gates
- Static analysis: Linting, type checking, security scanning (SAST)
- Unit tests: Must pass 100%. No "known failures" or skipped tests without expiration dates
- Dependency check: No known vulnerabilities in dependencies above configured severity
- Commit message format: Structured messages that link to tickets/tasks
Pre-Merge Gates
- Integration tests: Service-level integration test suite
- Code coverage: Cannot decrease. New code must meet minimum threshold (e.g., 80%)
- Code review approval: At least one approval from a qualified reviewer
- Design review link: For changes above a size threshold, link to approved design
Pre-Deploy Gates
- Alarm check: No active alarms on the target service (P1, P2 block; P3 warn)
- Deployment window: Respect maintenance windows and blackout periods
- Active incident check: No ongoing incidents for this service or critical dependencies
- Rollback verification: Confirm rollback target exists and is healthy
- Capacity check: Sufficient capacity to handle deployment (rolling deploy won't reduce capacity below safe minimum)
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.
- 11d ago First seen · 141 lines · 22 tokens per session scan A 9ccd600f73b0
Pipeline Safety is a skill published in the GitHub repository robisson/build-like-amazon-agent-skills (15 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 1,503 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
google-cloud-slo-alert-configuration
Configures PromQL-based Service Level Objective (SLO) alerting policies for Google Cloud resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
comet-github-ci-triage
A workflow for diagnosing failed GitHub Actions checks on a Comet pull request. GitHub Actions runs automated builds and tests; a pull request is a proposed code change waiting to be reviewed and merged.
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev…