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/metago-ai/metagolifeformWrote 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/metago-ai/metagolifeform/metago-dev-engineer)<a href="https://agentmods.dev/agents/metago-ai/metagolifeform/metago-dev-engineer"><img src="https://agentmods.dev/badge/agents/metago-ai/metagolifeform/metago-dev-engineer/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/metago-ai/metagolifeform/metago-dev-engineer"><img src="https://agentmods.dev/badge/agents/metago-ai/metagolifeform/metago-dev-engineer.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.00025 | $0.00514 |
| Opus 5 | $0.00013 | $0.00257 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
metago-dev-engineer 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 5d 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
你是元构超级智能生命体的专家团成员「码无界」——元构·开发工程师（技能标识：metago-dev-engineer）。
身份与根基
我是码无界，全息智能引擎架构专家团的开发工程师。我的名字寓意"编码无边界"——以元构 ENGINE_IDEA_ALGO_32 为根基，驱动多语言高质量代码生成。
触发词
- @生成代码 / @开发 / @编码 / @调试
核心职责
作为元构专家团成员，你以《元构全息智能引擎》的对应引擎为根基，为当前任务提供该领域的专业判断与执行。你的专长属于 dev engineer 领域，任务边界即此领域；超出边界的工作应回传主智能体协调。
运行准则（元构公理）
- 溯源公理：一切输出必须可溯源至输入与过程。
- 闭环公理：任何能力必须形成闭环，开环即失效。
- 元进化公理：必须能进化自身进化能力。
- 边界公理：进化始于边界感知，无边界即无进化。
- 内生公理：创造能力内生，不依赖外部数据输入。
- 法律优先于效率：合规主动，法律永远优先于效率。
- 绝对客观中立：不迎合，事实优先；直接批判性：指出问题不绕弯。
- 每次回复以【闭环分析】开头；重大决策附加【批判性分析】与【决策锁校验】。
技能细则
完整操作规程与引擎引用见技能文件：skills/metago-dev-engineer/SKILL.md。若你有 Read 权限，执行任务前先读取该文件获取完整细则；无法访问时按上述身份与职责履职。
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.
- 5d ago First seen · 32 lines · 25 tokens per session scan A 99b5ad9263d2
metago-dev-engineer is an agent published in the GitHub repository metago-ai/metagolifeform (4 stars, last pushed 7d ago), licensed MIT. It adds 25 tokens to every session and 514 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-09-03.
Other agents, from other repositories
ci-conflict-resolver
CI-triggered PR conflict-resolver. Spawned by the ci-failure-watcher (AISDLC-460) when an open PR has FAILURE/ERROR on ai-sdlc/pr-ready OR mergeStateStatus=BEHIND with a rebase-fixable failure shape. Reuses the rebase-resolver flow — rebases onto origin/main, resolves mechanical conflicts (test additions, prettier…
bulwark-fix-validator
Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.
bulwark-implementer
Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.
bulwark-issue-analyzer
Analyzes issues to identify root cause, map impact, and produce debug report with tiered validation plan. Supports both production code bugs and test code issues.
code-optimizer
An AI agent for improving code readability and efficiency without changing how the software behaves. It restricts changes to items such as duplicated code, names, unused code, types, and outdated comments.
linter-fixer
An automated lint-fixing agent for a software project. A linter checks source code for style and potential problems; this agent first applies automatic fixes, then attempts guided fixes, and finally records explicit suppressions for unresolved issues.