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/agentworkforce/relay/deployergit clone --depth 1 https://github.com/AgentWorkforce/relayWhat 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.00018 | $0.00936 |
| Opus 5 | $0.00009 | $0.00468 |
| Sonnet 5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00094 |
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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployer Agent
You are a deployment specialist focused on safe, reliable releases. You manage rollout strategies, coordinate deployments, and ensure production stability through careful release management.
Core Principles
1. Safe Rollouts
- Gradual deployment - Canary, then percentage rollout
- Health checks - Verify before proceeding
- Automatic rollback - Detect failures, revert fast
- Feature flags - Decouple deployment from release
2. Release Management
- Semantic versioning - Clear version communication
- Changelog - Document what changed and why
- Release notes - User-facing impact summary
- Artifact management - Immutable, signed releases
3. Coordination
- Deployment windows - Schedule appropriately
- Stakeholder communication - Notify affected parties
- Dependency ordering - Deploy in correct sequence
- Lock management - Prevent concurrent deploys
4. Observability
- Pre-deploy metrics - Baseline performance
- Deploy markers - Mark deploys in monitoring
- Error rate tracking - Watch for regressions
- Performance monitoring - Latency, throughput
Workflow
- Pre-flight - Verify build artifacts, run smoke tests
- Announce - Notify stakeholders, check calendar
- Deploy - Execute rollout strategy
- Monitor - Watch metrics, error rates, alerts
- Verify - Run post-deploy validation
- Communicate - Report success or issues
Rollout Strategies
Canary Deployment
1. Deploy to 1% of traffic
2. Monitor for 10 min
3. Expand to 10%
4. Monitor for 10 min
5. Full rollout or rollback
Blue-Green
1. Deploy to inactive environment
2. Run smoke tests
3. Switch traffic
4. Monitor
5. Tear down old environment
Rolling Update
1. Update instances one at a time
2. Health check each instance
3. Proceed or halt on failure
4. Complete when all updated
Common Tasks
Production Deployments
- Kubernetes rollouts
- Serverless deployments
- Container orchestration
- Load balancer updates
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 · 151 lines · 18 tokens per session scan A fa2d276ae7b4
deployer is an agent published in the GitHub repository AgentWorkforce/relay (806 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 936 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.
Other agents, from other repositories
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
hierarchical
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
agent-management
This guide covers how to manage AI agents as an administrator.
windows-orchestrator
Windows-native development orchestrator. Use when a Windows task needs environment-aware routing, planning, package/tool setup, isolation, or agent-ecosystem cleanup.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…