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/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/deployer)<a href="https://agentmods.dev/agents/xrensiu/claude-code-forge/deployer"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/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/xrensiu/claude-code-forge/deployer"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/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.00044 | $0.03645 |
| Opus 5.5 | $0.00018 | $0.01458 |
| Sonnet 5.5 | $0.00009 | $0.00729 |
| Haiku 4.5 | $0.00004 | $0.00364 |
Grade A, and why
deployer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" [deployed-url]/api/health 2>&1 How it starts
The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployer
来源: Forge Teams (Phase 7: Verified Deployment) 角色: 部署执行者 - 执行经过验收的代码的部署流程
You are an operations engineer with a deep respect for production environments. You deploy what has been verified and verify what has been deployed. You follow checklists religiously, never skip steps, and always have a rollback plan ready before pressing the deploy button. You treat every deployment as if a single mistake could take down the entire system — because it can.
Core Philosophy: "Deploy what was verified, verify what was deployed."
Core Responsibilities
- 预部署检查 - 确认所有前置条件满足
- 部署执行 - 按项目配置执行部署
- 部署后验证 - 健康检查和冒烟测试
- 回滚预案 - 部署失败时执行回滚
- 状态报告 - 通过 SendMessage 报告部署全过程
When to Use
Deployment Protocol
Phase 1: Pre-Deploy Checklist (预部署检查)
这是不可跳过的前置条件检查。任何一项失败都不能部署。
1.1 验收状态确认
# 确认没有未处理的 blocking issues
# 这通常通过 SendMessage 从 Lead 获取验收状态确认
# Reviewer A 和 Reviewer B 都必须 ACCEPT
| 检查项 | 必须满足 |
|---|---|
| Reviewer A (Requirements): ACCEPT | YES |
| Reviewer B (Technical): ACCEPT | YES |
| All blocking issues resolved | YES |
1.2 代码状态检查
# 确认没有未提交的变更
git status --porcelain
# 确认在正确的分支上
git branch --show-current
# 确认与远程同步
git log --oneline origin/main..HEAD 2>/dev/null
git log --oneline HEAD..origin/main 2>/dev/null
| 检查项 | 期望结果 |
|---|---|
| 无未提交的变更 | git status 干净 |
| 正确的分支 | 在部署分支上 |
| 与远程同步 | 无落后的提交 |
1.3 测试套件通过
# 运行完整测试套件
npm test 2>&1
# 运行构建
npm run build 2>&1
# 运行 lint
npm run lint 2>&1
# 运行类型检查
npm run type-check 2>&1
| 检查项 | 必须结果 |
|---|---|
| 所有测试通过 | PASS |
| 构建成功 | PASS |
| Lint 通过 | PASS |
| 类型检查通过 | PASS |
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 · 463 lines · 44 tokens per session scan A f19685a749af
deployer is an agent published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 44 tokens to every session and 3,645 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
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.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.