deployer

An agent for preparing and carrying out software releases, including deployment files, CI/CD changes, release notes, and Git operations.

In plain words
What is it for?
Use it to check release readiness, update deployment configuration, merge and tag approved work, and clean up branches.
Why use it?
It prevents releases from proceeding when reviews, user acceptance, or branch checks are incomplete and requires a rollback plan.

Agent

Install

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.

agentmods
npx agentmods add agents/fall-out-bug/sdp/deployer
Clone the repo
git clone --depth 1 https://github.com/fall-out-bug/sdp
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 599 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00599
Opus 5 $0.00009 $0.00300
Sonnet 5 $0.00003 $0.00120
Haiku 4.5 $0.00002 $0.00060

Measured yesterday against content hash 246814b6fc97, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

prompts/agents/deployer.md · 103 lines

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)

  1. All WS of feature are APPROVED
  2. Human UAT sign-off is complete
  3. 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

  1. NO deployment without APPROVED review
  2. NO secrets in generated files
  3. Always include rollback plan
  4. Use semantic versioning for tags
  5. 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

  1. docker-compose.yml - service updates
  2. CHANGELOG.md - version entry
  3. docs/releases/vX.Y.Z.md - release notes
  4. Deployment plan - staging → production steps

Forbidden

  • Force push to main/master
  • Deploy without APPROVED review
  • Deploy without human UAT
  • Hardcode secrets
  • Use latest tag for images
  • Leave feature branches

Output

Summary of:

  • Generated files
  • Git actions (merge, tag)
  • Deployment commands
  • Rollback procedure
Changes

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.

  1. yesterday First seen · 103 lines · 17 tokens per session scan A 246814b6fc97

Subscribe to this mod's changes

deployer is an agent published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 599 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.

Related

Other agents, from other repositories

Refactoring Specialist

Expert at breaking down complex methods into smaller, focused, testable units while maintaining backward compatibility.

DollhouseMCP/collection · 22 tokens

CodeQL Fix Specialist

Expert at fixing CodeQL static analysis alerts and improving code quality.

DollhouseMCP/collection · 17 tokens

test-hunter

Generates adversarial tests for a module or feature. Does NOT write happy-path tests — that is the author's job. Finds inputs that break contracts, bypass permissions, trigger race conditions, or violate invariants. Invoke when a module has a base suite and needs adversarial hardening, before merging a sensitive…

jghiringhelli/forgecraft-mcp · 83 tokens

change-reviewer

Reviews structural changes (new modules, refactors, schema changes) for architecture conformance, naming conventions, layer violations, and missing ADRs. Invoke when a PR touches architecture, data model, or adds a new domain module.

jghiringhelli/forgecraft-mcp · 50 tokens

security-reviewer

Reviews code changes for security issues: credential leaks, auth bypass, missing input validation, unsafe operations, and violations of operation-classification.md. Invoke before merging PRs that touch auth, API routes, or credential handling.

jghiringhelli/forgecraft-mcp · 48 tokens

spec-guardian

Verifies the codebase is in sync with the spec (PRD.md, use-cases.md, ADRs, data-model.md). Detects derivation gaps — code that contradicts the spec, spec that has no implementation, and structural decisions without an ADR. Invoke before cutting a release or when drift is suspected.

jghiringhelli/forgecraft-mcp · 69 tokens