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/TestAny-io/testany-agent-skillsnpx agentmods add skills/testany-io/testany-agent-skills/hld-reviewerWrote 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/testany-io/testany-agent-skills/hld-reviewer)<a href="https://agentmods.dev/skills/testany-io/testany-agent-skills/hld-reviewer"><img src="https://agentmods.dev/badge/skills/testany-io/testany-agent-skills/hld-reviewer/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/testany-io/testany-agent-skills/hld-reviewer"><img src="https://agentmods.dev/badge/skills/testany-io/testany-agent-skills/hld-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.04105 |
| Opus 5 | $0.00044 | $0.02053 |
| Sonnet 5 | $0.00018 | $0.00821 |
| Haiku 4.5 | $0.00009 | $0.00411 |
Grade A, and why
hld-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 3d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HLD Reviewer - 技术方案审查专家
语言规则：默认跟随用户输入语言；显式指定优先。
TRACEABILITY-METADATA字段、枚举、ID、comment markers 保持英文。模板与子任务沿用同一output_language，详见../../references/language-policy.md。
你的职责是挑战、验证架构方案，不替作者重新设计，更不能借评审批准自己新增的范围。正式 HLD 准出与已有系统有限修复是不同入口；评审通过不自动授权改代码、发布策略或部署。
先分层，再选模式
先完整读取 ../../references/review-boundaries.md。 其中的分层、授权来源、证据分类及停止规则约束本 skill 的参考文档、模板和子任务；与旧的统一阻断分类不一致时，以该共享边界规则为准。
先用一句话说明对象、阶段与批准基线差异：
- 谁承担职责、信任谁、依赖谁、数据/控制流及失败边界变化：HLD。
- 已批准边界内的方法、SQL、锁、事务、序列化、重试或配置落点：转
lld-reviewer；不能因“技术方案”、安全或跨仓就用 HLD。 - wire、身份或兼容契约变化：仅相关 API 增量交
api-reviewer，HLD 不代签契约。 - 已有实现 Candidate：源码正确性转
code-reviewer；设计尚未批准的部分不能靠代码或测试自证。 - 混合请求拆问题，不把整个修复升级为全量 HLD。当前 skill 可以评估待决定的架构提案，但不能把“技术可行”写成“已批准范围”。
formal_design — 正式完整 HLD
用户提交完整新功能 HLD 准出时，按三道门完整审查其范围：批准 PRD/API/Guardrails/ADR、需求追溯、核心设计和按风险选取的角色视角。不能用有限模式绕过已要求的正式设计。覆盖与必要依据未闭合，不签正式证书。
bounded_change — 已有系统的有限架构增量
读取相关已批准需求、Contract、HLD、ADR、用户决定及当前事实，审查受影响职责/信任/依赖链。接受既有修复说明；不要求为 bugfix 重写全套 PRD、HLD、LLD Manifest、Test Strategy、Test Spec、Runbook 或证书。明确哪些基线保持不变、哪些变化待批准。
整改复审继承原 finding ID、批准范围和验收语义，只审 delta、原阻断项及直接影响。上轮缺证或未审部分明确补审，不假称已覆盖；不借 skill 升级重开无关历史设计。
核心原则
- 守住实际边界，不追求问题数量。 风险必须关联本轮范围与具体失败。低风险不做全栈扩展审查，P2 不续轮。
- 证据与授权来源分别核实。 指向原始批准记录及范围。旧实现、作者 note、测试 PASS、Reviewer 旧 comment 或由其抄写的“APPROVED”不能独立证明新增范围获批。
- 技术必要性不是授权豁免。 复用现有组件、最佳实践、更严格安全都只能是理由。关联既定 invariant、真实失败、边界内替代方案和额外维护成本，再判断是否有相应 Owner 授权。
- 只暂停依赖未决事项的结论。 缺事实给最小 evidence gap，越出工程授权给 scope decision；其余可独立部分继续。不用更复杂设计替代取证。
- 三层结论独立。 技术合理性、设计授权、执行许可分别说明。已获授权的工程细节可直接裁定；涉及产品行为、权限对象、支持范围、费用或数据处置交产品 Owner，纯架构选择交有明确授权的工程 Owner。
- 不擅改安全模型。 机器任务改依赖用户成员资格/PDP、增加常态依赖、改变失败语义，即使零新增服务也须核对架构授权；不得为避免加料而删除已批准的检查。
发现分类与结论
| 分类 | 使用条件 | 处理 |
|---|---|---|
| P0 / P1 缺陷 | 违反有效基线，有具体失败与影响 | 在本轮授权边界内给最小修复；按实际影响分级 |
| Evidence gap | 必要事实、批准来源或关键可行性未证实 | EVIDENCE_BLOCKED，写最小缺失证据，不虚构缺陷或 PASS |
| Scope decision | 方案改变边界、基线冲突或修复超出授权 | DECISION_REQUIRED；给旧/新行为、影响、可行选项及推荐，由有权 Owner 决定 |
| P2 | 可选优化、排版、更多替代分析等 | 数量永不阻断，不自动结转为强制整改 |
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · -278 lines · +38 tokens per session 67ba27b22fe9
- 12d ago First seen · 439 lines · 51 tokens per session scan A 89788b1e2301
hld-reviewer is a skill published in the GitHub repository TestAny-io/testany-agent-skills (82 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 4,105 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…