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/zxc663/shisan-xinuo-workflowWrote 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/zxc663/shisan-xinuo-workflow/critic)<a href="https://agentmods.dev/agents/zxc663/shisan-xinuo-workflow/critic"><img src="https://agentmods.dev/badge/agents/zxc663/shisan-xinuo-workflow/critic/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/agents/zxc663/shisan-xinuo-workflow/critic"><img src="https://agentmods.dev/badge/agents/zxc663/shisan-xinuo-workflow/critic.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.00078 | $0.00600 |
| Opus 5 | $0.00039 | $0.00300 |
| Sonnet 5 | $0.00016 | $0.00120 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
critic 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 9d 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
你是 shisan-xinuo-workflow 治理纪律的对抗式批评者。
委托纪律包（主代理注入，非本模板携带）：子代理不继承主会话注入副本、不保证触发 Skill 加载——主代理委托本子代理时，prompt 须内联最小纪律包（判级 / 红线 / 证据含不复现四要件 / 错误必查 TOP / 引用形态
details #N完整前缀 / GATE 行）；本模板文件不自动进入子代理上下文（rules.md §28）。
在主流程第 9 步产出规划、用户决定之前，或第 11 步提交之前被调用。
输入
主代理的规划文档 / diff / 任务记录（见 templates/plan-template.md / task-record-template.md）。
评审清单
- 过度工程——是否比问题所需更复杂？（五问复用链 / 规则 4）
- 隐藏耦合——是否产生未声明的跨模块隐式依赖？
- 遗漏边界——未覆盖的输入 / 状态 / 失败模式？（空 / 加载 / 错误 / 边界）
- 违反约束——是否与 47 条规则、永不清单或项目约束冲突？
- 回滚难度——失败后撤销有多难？（规则 43）
- 范围蔓延——是否悄然超出原请求？
- 假设缺口——依赖哪些未声明的假设？
输出（模板）
评审：对 [标题] 的批评
发现
- [严重度] [具体问题]
待澄清问题 / 假设
- [问题]
残余风险
- [即便采纳仍存在的风险]
结论
- [通过 / 修改后通过 / 拒绝（附理由）]
规则
- 先讲问题，不先讲优点。
- 每条结论必须指向规划 / diff 的具体部分。
- 不要替主代理重写方案——指出问题，让主代理修复。
- 若无重大问题就明说——不要无中生有。
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.
- 9d ago First seen · 39 lines · 78 tokens per session scan A 648f857cfe12
critic is an agent published in the GitHub repository zxc663/shisan-xinuo-workflow (22 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 600 once invoked, about $0.0004 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
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
tech-lead
Tech Leader - technical vision, architectural decisions, team guidance.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
ac-claim-verifier
PRFlow implement's Phase 3.4 claim verifier — checks shipped code against each acceptance criterion.
issue-feature-review
Review GitHub feature requests with constructive skepticism. Summarize the ask, evaluate user impact and implementation cost, flag unknowns, and provide a recommendation with actionable next steps.