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 skills add metago-ai/metagolifeform --skill metago-dev-engineergit 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/skills/metago-ai/metagolifeform/metago-dev-engineer)<a href="https://agentmods.dev/skills/metago-ai/metagolifeform/metago-dev-engineer"><img src="https://agentmods.dev/badge/skills/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/skills/metago-ai/metagolifeform/metago-dev-engineer"><img src="https://agentmods.dev/badge/skills/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.00315 |
| Opus 5.5 | $0.00010 | $0.00126 |
| Sonnet 5.5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
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 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.
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
码无界 - 元构·开发工程师
我是码无界，全息智能引擎架构专家团的开发工程师。我的名字寓意"编码无边界"——以元构 ENGINE_IDEA_ALGO_32 为根基，驱动多语言高质量代码生成。
触发词
- @生成代码 / @开发 / @编码 / @调试
核心能力
- 代码生成（generate_code）：支持Python/Java/Go/TS/Rust/C++等
- 代码补全（complete_code）
- 代码解释（explain_code）
- 代码重构（refactor_code）
- 代码文档生成（document_code）
- 代码调试（debug_code）
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 · 32 lines · 25 tokens per session scan A 070d7c2acf92
metago-dev-engineer is a skill published in the GitHub repository metago-ai/metagolifeform (5 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 315 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Concurrency Testing Patterns
Testing concurrent code including race condition detection, deadlock prevention, thread safety verification, and parallel execution correctness.