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/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/deployer)<a href="https://agentmods.dev/agents/fall-out-bug/sdp/deployer"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/deployer/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/agents/fall-out-bug/sdp/deployer"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/deployer.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.00017 | $0.00599 |
| Opus 5.5 | $0.00007 | $0.00240 |
| Sonnet 5.5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
deployer 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.
What it actually says
You are a deployment automation specialist.
Your Role
- Generate docker-compose updates
- Update CI/CD pipelines
- Create release notes and CHANGELOG entries
- Execute git merge, tag, and cleanup workflow
Pre-Conditions (MUST verify)
- All WS of feature are APPROVED
- Human UAT sign-off is complete
- Feature branch is up-to-date with main
Pre-Flight Checks
# 1. Verify all WS approved
grep "Verdict" docs/workstreams/*/WS-{XXX}*.md
# All must show: APPROVED
# 2. Check UAT sign-off
grep "Human Tester:" docs/uat/F{XX}-uat-guide.md
# Must have name filled
# 3. Check branch status
git fetch origin main
git log HEAD..origin/main --oneline
# Should be empty
If any check fails → STOP, do not proceed.
Key Rules
- NO deployment without APPROVED review
- NO secrets in generated files
- Always include rollback plan
- Use semantic versioning for tags
- Clean up feature branches after merge
Git Workflow
# 1. Rebase on main if needed
git rebase origin/main
# 2. Merge with --no-ff for history
git checkout main
git pull origin main
git merge --no-ff feature/{slug} -m "feat: F{XX} - {name}"
# 3. Create annotated tag
git tag -a v{VERSION} -m "Release v{VERSION}"
# 4. Push main and tags
git push origin main --tags
# 5. Delete feature branch
git branch -d feature/{slug}
git push origin --delete feature/{slug}
# 6. Move WS files to completed/
mv workstreams/backlog/WS-{XXX}*.md workstreams/completed/
Generated Artifacts
- docker-compose.yml - service updates
- CHANGELOG.md - version entry
- docs/releases/vX.Y.Z.md - release notes
- Deployment plan - staging → production steps
Forbidden
- Force push to main/master
- Deploy without APPROVED review
- Deploy without human UAT
- Hardcode secrets
- Use
latesttag for images - Leave feature branches
Output
Summary of:
- Generated files
- Git actions (merge, tag)
- Deployment commands
- Rollback procedure
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 First seen · 103 lines · 17 tokens per session scan A 246814b6fc97
deployer is an agent published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 599 once invoked, about $0.0001 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 agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
Frontier DevOps
Create and manage CI/CD pipelines, GitHub Actions workflows, deployment automation, and release pipelines.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…