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/synaptic-ai-consulting/AAMADWrote 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/rules/synaptic-ai-consulting/aamad/delivery-workflow)<a href="https://agentmods.dev/rules/synaptic-ai-consulting/aamad/delivery-workflow"><img src="https://agentmods.dev/badge/rules/synaptic-ai-consulting/aamad/delivery-workflow/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/rules/synaptic-ai-consulting/aamad/delivery-workflow"><img src="https://agentmods.dev/badge/rules/synaptic-ai-consulting/aamad/delivery-workflow.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.00734 | $0.00734 |
| Opus 5.5 | $0.00294 | $0.00294 |
| Sonnet 5.5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
delivery-workflow 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 1mo 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AAMAD Delivery Workflow (Phase 3: Deliver)
Purpose
- Operationalize the validated MVP after Build-phase artifacts are complete.
- Govern the DevOps Engineer persona (
@devops.eng) and the single deliver artifactproject-context/3.deliver/deploy.md.
Phase Gate
- Do not start Deliver work until
project-context/2.build/qa.mdexists and documents MVP verification results (pass or explicitly scoped known gaps). - Prefer
project-context/2.build/evals.mdfrom@qa.engbefore Deliver; its Production Monitoring Recommendations feed deploy.md's monitoring/observability config. If missing, continue and record the gap under deploy.md Assumptions. - Prefer
project-context/2.build/security.mdfrom@security.engbefore Deliver. If security.md is missing, continue only when the operator accepts the gap and record it under deploy.md Assumptions (required whenaamad.config.ymlsetssecurity.require_security_assessment: true). - Required inputs: qa.md, backend.md, frontend.md, integration.md, PRD, and SAD (including DevOps and Deployment Architecture). Optional but recommended: evals.md, security.md.
- On missing prerequisites, halt and write a Diagnostic section in deploy.md with blockers and safe retry steps.
Deliver Module Structure
Execute delivery in focused steps with fresh context when possible:
- Release readiness — QA, evals, and security gate check and release notes (
*prepare-release). - Deploy definition — Runtime-aligned container or platform config (
*define-deploy). - CI scaffolding — Minimal lint/test/build pipeline config only (
*configure-cicd). - Runbook — Hosting, env matrix, access control, rollback (
*document-deploy). - User documentation — Installation guide and user manual (
*document-user-guide→user-guide.md).
Continuous Deployment Policy
- Generate CI/CD configuration files only; do not trigger live deploys without explicit operator authorization.
- Pipelines must run lint, test, and build stages appropriate to the stack defined in setup.md and backend.md.
- Document manual promotion steps and rollback procedure in deploy.md.
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.
- 1mo ago Changed · +1 lines · +56 tokens per session de6b5b9d01db
- 1mo ago First seen · 49 lines · 678 tokens per session scan A 08f61f0ad67d
delivery-workflow is a cursor rule published in the GitHub repository synaptic-ai-consulting/AAMAD (86 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 734 tokens to every session, about $0.0029 per session on Opus 5.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 cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
cursor-asdd
ASDD contribution rules for this repository.
agents
Agent engineering standards — Agents (TR-SEC-003).
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
infrastructure
Terraform infrastructure-as-code standards for multi-cloud (AWS, GCP, Azure, OCI) provisioning.