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.
npx agentmods add skills/unknowbug/anchorlaw/anchor-testnpx skills add unknowbug/anchorlaw --skill anchor-testgit clone --depth 1 https://github.com/unknowbug/anchorlawWrote 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/unknowbug/anchorlaw/anchor-test)<a href="https://agentmods.dev/skills/unknowbug/anchorlaw/anchor-test"><img src="https://agentmods.dev/badge/skills/unknowbug/anchorlaw/anchor-test.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.00035 | $0.00384 |
| Opus 5 | $0.00017 | $0.00192 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
anchor-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 yesterday.
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.
This is a copy
89% identical to anchor.test — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
anchor.test — 运行验证
Protocol: spec/protocol-v0.20.md §5.4 (Anchor Health States), §9 (Degraded Verification) Layer: L2 (Anchors) Execution: inline
触发场景
添加 anchor 后验证、CI 失败排查时。
操作步骤
- 运行（CLI，§14.4）：
anchorlaw test [module]（-v显示完整 traceback）。 - 按健康状态解读（§5.4）：
healthy→ 通过，声称已验证degrading→ 有测试失败：之前验证过的行为坏了 → 修复或更新 anchor，不得静默unverified→ 只有 idk：探索区，正常stale_unknown→ idk 超 90 天且函数改过（§5.3）→ 升级处理uncompilable→ 代码无法独立编译 → 按 §9 降级验证分类（Full/Partial/Degraded）处理，不硬跑
- 无法独立编译的代码先按 §9 分类模式，再决定能否运行。
输出
测试结果 + 每函数健康状态。
约束
- 只通过 CLI 运行（§14.4）。
- 失败不掩盖：degrading 如实报告。
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.
- yesterday Changed a762dd2f3a25
- 5d ago First seen · 36 lines · 35 tokens per session scan A acb3ee3813d8
anchor-test is a skill published in the GitHub repository unknowbug/anchorlaw (5 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 384 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to anchor.test, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
openspec-plus-apply
MANDATORY skill that activates whenever the OpenSpec apply phase begins. Triggers: /opsx-apply runs, the openspec-apply-change vanilla skill is referenced or active, openspec instructions apply is invoked, or the user asks to implement, apply, execute, or build out an OpenSpec change ('implement the change', 'apply…
openspec-plus-design
MANDATORY skill that activates whenever the OpenSpec design phase begins. Triggers: /opsx-new or /opsx-continue runs; openspec-new-change, openspec-continue-change, or openspec-explore is active; openspec instructions design is invoked; or the user wants to create, update, review, refine, or discuss an OpenSpec design…
openspec-plus-spec
MANDATORY skill that activates whenever the OpenSpec specification phase begins. Triggers: /opsx-new or /opsx-continue runs; openspec-new-change, openspec-continue-change, or openspec-explore is active; openspec instructions spec or openspec instructions specs is invoked; or the user wants to create, update, review…
openspec-plus-tdd
MANDATORY skill that activates whenever code is written to implement an OpenSpec change task. Triggers: openspec-plus-apply is active, /opsx-apply is running, the user is implementing tasks from an OpenSpec change, an implementer subagent dispatched by openspec-plus-apply is starting work, or the user invokes phrases…
openspec-plus-proposal
MANDATORY skill that activates whenever the OpenSpec proposal phase begins. Triggers: /opsx-new or /opsx-continue runs; openspec-new-change, openspec-continue-change, or openspec-explore is active; openspec instructions proposal is invoked; or the user wants to create, update, review, refine, or discuss an OpenSpec…
openspec-plus-tasks
MANDATORY skill that activates whenever the OpenSpec tasks phase begins. Triggers: /opsx-new or /opsx-continue runs; openspec-new-change, openspec-continue-change, or openspec-explore is active; openspec instructions tasks is invoked; or the user wants to create, update, review, refine, or discuss an OpenSpec tasks.md…