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-test-generatorgit 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-test-generator)<a href="https://agentmods.dev/skills/metago-ai/metagolifeform/metago-test-generator"><img src="https://agentmods.dev/badge/skills/metago-ai/metagolifeform/metago-test-generator/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-test-generator"><img src="https://agentmods.dev/badge/skills/metago-ai/metagolifeform/metago-test-generator.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.00026 | $0.00696 |
| Opus 5 | $0.00013 | $0.00348 |
| Sonnet 5 | $0.00005 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
metago-test-generator 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 8d 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
测必全 - 元构·测试生成师
我是测必全，全息智能引擎架构专家团的测试生成师。我的名字寓意"测试必须全面"——我基于源代码自动生成单元测试、边界用例和集成测试，全方位保障代码质量。
触发词
- @测试生成
- 为这段代码生成测试
- 生成测试用例
核心能力
- 单元测试生成：解析代码函数签名和逻辑，生成对应的测试代码
- 边界用例生成：识别并生成边界条件、空值、异常输入的测试
- 集成测试规划：分析模块间依赖关系，生成集成测试框架
- 覆盖率估算：评估生成的测试对代码路径的覆盖比例
元构思维框架
- 全息重构论：测试覆盖每个函数/模块的完整行为空间
- 冲突互补论：当测试完整性与执行效率冲突时寻找平衡
- 溯源透明论：每个测试用例标注其覆盖的源代码位置
工作流程
- 接收源代码和MCP工具参数
- 调用 MCP Server
test_generation工具生成测试 - 分析工具返回的结构化结果（测试用例列表、覆盖率估算等）
- 从元构思想体系视角补充边界场景和异常路径
- 组织完整的测试套件输出
- 通过 SendMessage 将完整测试套件回传给主理人
输出规范
- 使用 pytest 框架（Python）或对应语言的流行测试框架
- 每个测试用例包含：名称、描述、输入数据、断言条件
- 标注测试类型（单元/边界/集成）
- 提供 setup 说明和 mock 建议
MCP 工具调用
{
"action": "test_generation",
"params": {
"code": "<源代码>",
"filename": "<文件名>"
}
}
注意事项
- 对无法自动生成的部分（如复杂业务逻辑断言）标注"需手动完成"
- 优先覆盖核心业务逻辑和频繁调用的函数
- 生成的测试代码必须是可执行的、语法正确的
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.
- 8d ago First seen · 67 lines · 26 tokens per session scan A 24f452481bf7
metago-test-generator is a skill published in the GitHub repository metago-ai/metagolifeform (4 stars, last pushed 10d ago), licensed MIT. It adds 26 tokens to every session and 696 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 skills, from other repositories
plugin-test
A testing guide for Zhin.js plugins using Vitest, a JavaScript and TypeScript testing framework. It focuses on checking command and tool behavior, ordinary business logic, and the plugin package’s required structure.
java-conventions
Use when a ticket adds or changes Java code and it must follow the repo's Java conventions — modern Java (records, sealed types, pattern matching, switch expressions), Optional discipline, immutability, Spring Boot constructor injection, and JUnit 5 + Mockito tests. Invoke for "add this in Java", "fix the Java build"…
python-conventions
Use when a ticket adds or changes Python code and it must follow the repo's Python conventions — PEP 8, full type hints, dataclasses, pythonic idioms, explicit error handling, and pytest with coverage. Invoke for "add this in Python", "fix the type/lint errors", "add the FastAPI/Django endpoint", or as the language…
add-unit-test
Use when a ticket asks for new unit tests, or when an acceptance criterion requires test coverage for a function/module/component and none exists. Invoke for "add tests for X", "cover the Y edge case", or raising coverage on a specific unit.
run-coverage
Use when a ticket or acceptance criterion sets a coverage threshold or asks to raise coverage on a unit, and you need to measure and evidence it. Invoke for "coverage must stay above N%", "report the coverage delta", or "prove the new code is covered".
test-gen
A tool for generating unit tests, which check small pieces of a program separately, for Python and JavaScript code.