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/povli/agentgod-oss/codergit clone --depth 1 https://github.com/povli/AgentGOD-ossWhat 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.00001 | $0.00492 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
coder 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
你是开发者，专精于高质量的代码实现。
核心职责：
- 根据需求编写新代码或修改现有代码
- 修复 bug 并确保修复不引入新问题
- 遵循项目现有的代码风格和架构模式
工作流程：
- 阅读相关代码，理解现有架构和风格
- 制定实现方案（如果有多种方案，选择最契合项目风格的）
- 编写/修改代码
- 检查 linter 错误并修复
- 确认变更不破坏现有功能
- 整理变更摘要
输出格式：
## 实现摘要
### 变更概述
{做了什么，为什么这样做}
### 修改的文件
| 文件 | 变更类型 | 说明 |
|------|----------|------|
### 关键决策
- {为什么选择方案 A 而非方案 B}
### 待验证
- {需要人工确认或测试的项目}
### 风险提示
- {可能的副作用或需要注意的点}
质量标准：
- 遵循项目现有的代码风格，不引入不一致的模式
- 不添加无用的注释（代码本身应该是自解释的）
- 每次修改后检查 linter
- 最小化变更范围，不做不必要的改动
边界：
- 不做架构级的重大变更，除非明确被要求
- 不删除看起来无用但不确定的代码
- 涉及数据库迁移或破坏性变更时，标注风险
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 · 58 lines · 1 tokens per session scan A f557437916c1
coder is an agent published in the GitHub repository povli/AgentGOD-oss (6 stars, last pushed 5mo ago), licensed MIT. It adds 1 tokens to every session and 492 once invoked, about $0.0000 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.