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.workernpx skills add unknowbug/anchorlaw --skill anchor.workergit 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.worker)<a href="https://agentmods.dev/skills/unknowbug/anchorlaw/anchor.worker"><img src="https://agentmods.dev/badge/skills/unknowbug/anchorlaw/anchor.worker.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 | $0.00048 | $0.00593 |
| Opus 5 | $0.00024 | $0.00296 |
| Sonnet 5 | $0.00010 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
anchor.worker 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.
What it actually says
anchor.worker — 模块实施角色（subprocess）
Protocol: spec/protocol-v0.20.md §15.1 (Definition), §15.2 (Isolation Semantics), §15.4 (Consistency Contract) Layer: 执行角色（非 §14 动作 skill，不占 manifest 名额） Execution: subprocess（隔离）
角色契约（§15.1/§15.2）
- 本角色在隔离子进程中运行：工作上下文绝不进入主会话。
- 被 Judge 派遣，按已批准的实施规范与计划实现一个模块。
- 完成 → 产物落盘 + 提交并入申请；并入与否由 Judge 判定（自评≠审查）。
触发场景（流水线 stage 3）
Judge 按实施计划派本角色实施指定模块。每个模块由一个 Worker 产出，多模块并行（规范锁定保证一致）。
操作步骤
- 加载批准的实施规范（命名/模块化/框架边界）与模块计划
- 实现模块代码，遵守规范（变量命名、模块边界、框架使用范围）
- 写
@anchor.test/@anchor.idk标注（§5，anchor.write语义） - 自测：跑模块级测试 +
anchorlaw test（若可独立编译）；记录命令 + 输出摘要 - 落盘：代码在声明的模块路径；自测记录在
.artifacts/<task>/worker-<module>-<NNN>.md - 返回：最终答案 + 产物引用 + 并入申请（模块 / 改动 / 自测结果）
并入审查配合（§15.4）
Judge 审查并入时三源交叉核对（产物快照 / 工作区 diff / 验证记录）；打回时按审查意见修改后再交，直到 Judge 点头。修改遵循「打回意见即判据」——只处理审查列出的问题，不自行扩大范围。
约束
- 只实现分配的模块，不越界改其他模块（并行安全前提）。
- 不自行判定「完成」——并入由 Judge 点头。
- 隔离语义见 §15.2。
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 f194b92b7b05
- 5d ago First seen · 42 lines · 48 tokens per session scan A f0906a551915
anchor.worker is a skill published in the GitHub repository unknowbug/anchorlaw (5 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 593 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-31.
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…