AI-DLC Workflows is a reusable software-development lifecycle that guides AI coding agents through staged engineering work and human approval gates. Teams use it to run structured, reviewable development processes across several coding-agent environments, and the catalogue entries are its agents, skills, rules, MCP integrations, and instructions.
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/awslabs/aidlc-workflowsWrote 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/agents/awslabs/aidlc-workflows/aidlc-pipeline-deploy-agent)<a href="https://agentmods.dev/agents/awslabs/aidlc-workflows/aidlc-pipeline-deploy-agent"><img src="https://agentmods.dev/badge/agents/awslabs/aidlc-workflows/aidlc-pipeline-deploy-agent.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.00041 | $0.01282 |
| Opus 5 | $0.00020 | $0.00641 |
| Sonnet 5 | $0.00008 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
aidlc-pipeline-deploy-agent 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 5d 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.
The source is not reproduced here
Licensed MIT-0
The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 5d ago First seen · 82 lines · 41 tokens per session scan A 4e6475440724
aidlc-pipeline-deploy-agent is an agent published in the GitHub repository awslabs/aidlc-workflows (4,395 stars, last pushed today), licensed MIT-0. It adds 41 tokens to every session and 1,282 once invoked, about $0.0002 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-09-02.
Other agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.
cicd-specialist
CI/CD expert for GitHub Actions, GitLab CI, and Forgejo. Use for pipeline creation, testing workflows, and release automation.
release-engineer
Release engineer. Configures the CLI tool's build, packaging, and deployment pipeline. Sets up deployment to PyPI/npm/Homebrew/GitHub Releases.