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-routerWrote 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-router)<a href="https://agentmods.dev/skills/zuoyebang/aiweave/new-router"><img src="https://agentmods.dev/badge/skills/zuoyebang/aiweave/new-router/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-router"><img src="https://agentmods.dev/badge/skills/zuoyebang/aiweave/new-router.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.00027 | $0.00781 |
| Opus 5.5 | $0.00011 | $0.00312 |
| Sonnet 5.5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
new-router 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
根据 $ARGUMENTS 生成路由注册文件。
公共步骤模板见 skills-spec/01_skill_authoring_guide.md §A-§E。本 Skill 特定内容如下。
第 0 步:拒绝规则与依赖前置
- ⛔ 拒绝(§A.1):生成 admin 路由组时必须跳过
BUILD_STATUS.md§0 中 🚫 模块对应路由(即使routing.md§5 表中列出也不能注册,可以注释占位 + 标注 "🚫 ...") - 状态检查(§A.2):读
BUILD_STATUS.md§2 router 行 - 依赖(§A.3):扫描
controllers/http/{audience}/下文件,缺失的 controller 先列清单提醒用户
第 1 步:读取设计文档(公共必读见 §B)
- 主文档:
docs/architecture/routing.md§3(注册代码)+ §5(完整路由表) - 确认每条路由的:HTTP 方法 / 路径 / 控制器函数 / 校验中间件
- 确认包导入别名约定(§4)
第 2 步:生成路由文件
http.go 主入口
package router
import (
"{project}/controllers/http/probe"
"{project}/middleware"
"{project}/pkg/gin"
)
func Http(engine *gin.Engine) {
engine.Use(middleware.Cors)
engine.Use(middleware.Metrics)
engine.GET("/{prefix}/ready", probe.Ready)
registerInternalRoutes(engine)
registerOperatorRoutes(engine)
registerAdminRoutes(engine)
}
http_{audience}.go 子文件
按 routing.md §3.2 代码结构生成,例:
func registerOperatorRoutes(engine *gin.Engine) {
op := engine.Group("/{prefix}/operator")
// 免校验
op.POST("/{module}/{action}", {audience}_{module}.{Action})
// 需校验
protected := op.Group("")
protected.Use(middleware.{UserMw}())
{
registerOperator{Module}Routes(protected)
}
}
第 3 步:文档同步(公共项见 §C)
- 确认
routing.md§5 路由表与代码完全一致(含 🚫 跳过项注释) - 更新 BUILD_STATUS §2 router 行
第 4 步:测试同步(4 类用例标准见 §D)
路由是连接层,测试通过下游接口用例间接覆盖:
cd test && go test -v ./cases/{audience}/...
如生成 admin 组:必须验证 cases/admin/{disabled-module}_blocked_test.go smoke 用例(验证 /admin/{disabled-module}/* 返回 404)。
第 5 步:验证(公共格式见 §E)
go build ./router/...
go vet ./router/...
🧩 AIWeave 骨架 · 作者 XuRuibo [email protected] · Apache-2.0 · 模板文件,复制到工程后按业务语义填充
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 · 95 lines · 27 tokens per session scan A 3581f230558b
new-router is a skill published in the GitHub repository zuoyebang/aiweave (20 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 781 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
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
compact-error-handling
Reduce repeated exception-handling code with language-appropriate constructs while preserving error propagation and diagnostics.
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…
api-contract-review
Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).
backend-system-design
Produce a staff-grade backend system-design RFC: a 12-section document for a new service, endpoint, or feature. Composes with slo-define, performance-budget, api-contract-review, release-plan. Use when a backend feature needs architecture-level design before planning. Do not use to slice a designed change (use…
graphql-contract-review
Review a GraphQL schema and a Backend-for-Frontend (BFF) contract BEFORE implementation against a GraphQL checklist (nullability, N+1, cost limits, federation, BFF thinness). Use when designing or modifying a GraphQL schema, a federated subgraph, or a BFF contract. Do not use for a REST contract (use…