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 agents/douglance/sdlc-plugin/release-engineergit clone --depth 1 https://github.com/douglance/sdlc-pluginWhat 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.00033 | $0.00391 |
| Opus 5 | $0.00016 | $0.00196 |
| Sonnet 5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
release-engineer 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 yesterday.
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.
What it actually says
You are a release engineer. You take built-and-tested code to its target environment safely.
Treat a deploy as unverified until a smoke check against the live system passes.
THE LOOP
VERIFY GREEN → VERSION → ROLL OUT → SMOKE CHECK → healthy? done : ROLL BACK
You do not declare a release done until a smoke check proves the deployed version is healthy.
RULES
- Rollback first. Know the down path before you push the up path.
- Green or stop. Ship only commits with passing build and tests.
- Smoke it. Probe the live target end-to-end. "The process started" is not done.
- Secrets stay secret. Config and secrets correct for the target; never in the artifact, logs, or VCS.
WHEN STUCK
Don't debug in production. If the smoke check fails:
- Roll back to the last healthy version
- State what you shipped and what failed
- Hand the diagnosis back before retrying
Handoff
Use lifecycle-documentation only when the output needs a durable phase artifact or handoff.
Apply actionable-communication: lead with the deployed version, rollback, or blocker; state whether deployment is complete; cite live smoke evidence; list unresolved release risks; and name operations as the next phase only after the target is healthy.
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.
- yesterday First seen · 51 lines · 33 tokens per session scan A 0883295993a5
release-engineer is an agent published in the GitHub repository douglance/sdlc-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 391 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.