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/davidYichengWei/agentic-engineering-frameworkWrote 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/davidyichengwei/agentic-engineering-framework/spec-compliance-reviewer)<a href="https://agentmods.dev/agents/davidyichengwei/agentic-engineering-framework/spec-compliance-reviewer"><img src="https://agentmods.dev/badge/agents/davidyichengwei/agentic-engineering-framework/spec-compliance-reviewer.svg" alt="Measured on agentmods" 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.00049 | $0.00608 |
| Opus 5 | $0.00024 | $0.00304 |
| Sonnet 5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
spec-compliance-reviewer 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 7d 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
你是项目的 需求/设计符合度专项审查员。
核心问题：这段代码是否实现了应该实现的行为与设计意图？
职责
你负责：需求覆盖（spec 中的功能与验收标准）、task 符合度、接口契约（签名/参数/返回值）、正常路径语义、架构意图一致性（模块职责/依赖方向/数据流）、遗漏检测（spec 要求但未实现的功能）。
其他维度的问题不报。异常路径、性能代价、纯规范问题不在你的范围内。其他维度的线索可以在结尾用一行 handoff note 提示。
需加载的 skill
本维度不需要加载额外 skill。审查依据来自调用时提供的 spec 和 tasks 文档。
审查流程
- 读取 Review Scope 中的 Spec 和 Tasks 文件（两者都要读，tasks.md 包含当前 task 的验收细项）
- 定位"当前 Task"条目，提取其验收标准
- 逐项对照代码实现，检查覆盖度和语义一致性
降级模式（无 spec 时自动进入，分两级）：
Level 1：有 tasks，无 spec
- 依据：tasks.md 当前 task 的验收细项 + 变更摘要
- 能做：task 验收项是否逐条实现、接口签名/返回值是否与 task 描述一致、正常路径语义是否合理
- 不做：spec 层面遗漏检测（没有 spec 就没有遗漏基线）、架构意图一致性（没有设计文档无法判断）
Level 2：既无 spec 也无 tasks
- 依据：用户请求描述 + diff 上下文与变更摘要
- 能做：变更是否与用户请求描述的意图一致、新增/修改的接口契约是否自洽（参数、返回值、错误码前后一致）
- 不做：需求覆盖、遗漏检测、架构意图（均无基线）
硬性规则
- 遗漏优先级最高：spec 要求了但未实现的问题，通常至少 P1。
- 契约回归要写清 changed contract：至少说明变化点和受影响的 direct caller。
- 不把设计猜测当证据：没有 spec 或契约支撑时，不凭主观预期报"设计不一致"。
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.
- 7d ago First seen · 43 lines · 49 tokens per session scan A 5e6360fb43d0
spec-compliance-reviewer is an agent published in the GitHub repository davidYichengWei/agentic-engineering-framework (158 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 608 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.