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 skills add unknowbug/anchorlaw --skill anchor.conceptsgit 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.concepts)<a href="https://agentmods.dev/skills/unknowbug/anchorlaw/anchor.concepts"><img src="https://agentmods.dev/badge/skills/unknowbug/anchorlaw/anchor.concepts.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.00043 | $0.00456 |
| Opus 5 | $0.00022 | $0.00228 |
| Sonnet 5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
anchor.concepts 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- anchor-concepts — 89% identical, 3 lines differ
What it actually says
anchor.concepts — Anchor 语义速查
Protocol: spec/protocol-v0.20.md §5 (Anchor Semantics), §13 (Anchor Abstraction) Layer: L0 (Concepts) — 仅作语义参考，自身不执行任何操作 Execution: inline
触发场景
写或审查 anchor 标注之前，需要 anchor 语义定义时调用本 skill（供 L1–L4 引用）。
核心语义
- @anchor.test = 可验证声称：
description（人类可读）+test_fn（可执行谓词）+source（必填，v0.3+） - @anchor.idk = 诚实边界声明：
what（具体未知项），source可选 - source 类型（§5.5）：
trace/memory允许 @test；static仅允许 @idk。@test 无 source 或 static → INVALID - staleness（§5.3）：@idk 超 90 天且函数已修改 → 升级为 WARNING
- 健康状态（§5.4）：
healthy/unverified/degrading/stale_unknown/skeleton/uncompilable - 三语言等价（§13）：Python 装饰器 / TypeScript JSDoc 注释 / C++ 行注释
// @anchor.*，验证载体可不同（test_fn / assert / probe binary）
输出
一份语义澄清：回答当前任务涉及的 anchor 语义问题。不写代码、不跑命令。
约束
- 写 anchor 用
anchor.write；验证用anchor.test；本 skill 只回答「是什么」。
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.
- 4d ago Changed 033903e5dae2
- 8d ago First seen · 32 lines · 43 tokens per session scan A 73c4a7817319
anchor.concepts is a skill published in the GitHub repository unknowbug/anchorlaw (5 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 456 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
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…