Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/zuoyebang/aiweavenpx agentmods add skills/zuoyebang/aiweave/new-testWrote 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/zuoyebang/aiweave/new-test)<a href="https://agentmods.dev/skills/zuoyebang/aiweave/new-test"><img src="https://agentmods.dev/badge/skills/zuoyebang/aiweave/new-test/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/zuoyebang/aiweave/new-test"><img src="https://agentmods.dev/badge/skills/zuoyebang/aiweave/new-test.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.00035 | $0.01080 |
| Opus 5.5 | $0.00014 | $0.00432 |
| Sonnet 5.5 | $0.00007 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
new-test 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
为 $ARGUMENTS 生成 test/cases/ 下的接口级测试文件。
公共步骤模板见 skills-spec/01_skill_authoring_guide.md §A-§E。本 Skill 特定内容如下。
职责:补齐遗漏的测试。正常流程下,
/new-service//new-controller在生成业务代码时就应同步测试。本 Skill 仅在发现某接口代码已有但测试缺失时使用。
第 0 步:拒绝规则与依赖前置
- ⛔ 拒绝(§A.1):接口路径命中
BUILD_STATUS.md§0 中 🚫 模块时立即拒绝 - 状态检查(§A.2):读
BUILD_STATUS.md§5 → handler 必须已实现(🟢);未实现 → 停止,提示先/new-controller - 依赖(§A.3):
- 读
docs/testing/testing_design.md§4 确认框架 API 签名 - 读
test/fixtures/seed/README.md熟悉 seed 数据
- 读
第 1 步:读取设计文档(公共必读见 §B)
- 主文档:
docs/api/{audience}_interfaces.md - 提取:请求参数 / 响应结构 / 校验规则 / 错误码映射
第 2 步:生成测试文件
文件路径:test/cases/{audience}/{module}_{action}_test.go
按 §D 的 4 类用例模板生成(每类至少 1 个 sub test):
package {audience}_test
import (
"testing"
"{project}/test/framework"
)
func Test{Action}_Succ(t *testing.T) {
body := map[string]interface{}{ /* 合法参数 */ }
resp := framework.{Audience}Post(t, "{path}", {auth}, body)
framework.AssertSucc(t, resp)
framework.AssertJSONField(t, resp.{Audience}.Data, "xxx", "expected")
}
func Test{Action}_MissingXxx_Expected{Code}(t *testing.T) {
body := map[string]interface{}{ /* 缺字段 */ }
resp := framework.{Audience}Post(t, "{path}", {auth}, body)
framework.AssertFail(t, resp, {errCode})
}
func Test{Action}_{Module}Disabled_Expected{Code}(t *testing.T) {
// seed 中状态为禁用的 {核心实体}
resp := framework.{Audience}Post(t, "{path}", {edge case auth}, body)
framework.AssertFail(t, resp, {errCode})
}
func Test{Action}_WritesMysqlAndRedis(t *testing.T) {
resp := framework.{Audience}Post(t, "{path}", {auth}, body)
framework.AssertSucc(t, resp)
framework.AssertMysqlExists(t, "{example_db}", "{example_table}", "field = ?", value)
framework.AssertRedisHashField(t, "{ns}:info:"+entityId, "status", "1")
}
第 3 步:接入 TestMain
每个 cases/{audience}/ 子包应有 common_test.go 提供 TestMain。新增测试文件不重复写。如是新路由组的第一个文件,先创建:
package {audience}_test
import (
"os"
"testing"
"{project}/test/framework"
)
func TestMain(m *testing.M) {
code := framework.RunTests(m)
os.Exit(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 · 110 lines · 35 tokens per session scan A 3476747e83d8
new-test is a skill published in the GitHub repository zuoyebang/aiweave (20 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,080 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-30.
Other skills, from other repositories
ai-feature-eval-harness
Design an eval plan for a product AI feature: success criteria, a held-out labeled dataset, per-criterion grading (code-based, then LLM-based), and a pass threshold. Use when a task ships or changes a feature with non-deterministic model output (classification, extraction, summarization, ranking, agent action) needing…
api-runtime-verify
Verify a built backend HTTP surface at runtime: per route, record the response, assert it against the slice's acceptance behavior, and decide PASS/FAIL/BLOCKED. Do not use to review a contract before implementation (use api-contract-review or graphql-contract-review), write code (use implement-approved-slice), triage…
app-runtime-verify
Verify a mobile or app runtime: run the app (device, emulator, or headless), read captured output (logcat, iOS device log, or Metro/JS console), classify errors per stack, and decide a PASS/FAIL gate. Adapters: React Native/Expo, Unity mobile. Do not use to plan a screen (use implementation-plan), to write or fix code…
post-deploy-verifier
Per-slice post-deploy verification plan: acceptance criteria mapped to live signals, plus rollback triggers. Activates after a deploy with no plan, when branch-commit made a deploy without checks, or when slice-closure would close a slice without one. Do not use before the slice ships (use verify-against-rubric), for…
test-strategy
Define the smallest set of meaningful tests that protects behavior and reduces the regression risk for the active task, persisted as TESTSTRATEGY.md. Use when a change affects behavior, contracts, data flow or regression risk, or auth, biometric or runtime-risk scope lacks one, even if small. Do not use when the…
web-runtime-verify
Verify a built web frontend at runtime: serve the build, assert page identity, run the web battery (overflow 320 to 2560, keyboard, console, Lighthouse, axe), and decide a PASS/FAIL/BLOCKED gate. Fixes are routed, not applied. Do not use to plan (implementation-plan), write code (implement-approved-slice), for perf…