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 commands/xcodethink/open-claude-code-skills/anchorgit clone --depth 1 https://github.com/xcodethink/open-claude-code-skillsWrote 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/commands/xcodethink/open-claude-code-skills/anchor)<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/anchor"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/anchor.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.00030 | $0.00337 |
| Opus 5 | $0.00015 | $0.00169 |
| Sonnet 5 | $0.00006 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
anchor 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.
What it actually says
anchor — 新对话开场 / 项目锚定
用户输入 /anchor $ARGUMENTS 触发 项目锚定四要素(防猜项目 / 防 4-08 跨项目误删事故)。
立刻读取并完整加载:
~/.claude/prompts/lib/09-元指令/新对话锚定.md
按其"行为契约"段严格执行:
- 未拿到 4 项前禁止动手:项目 + 当前状态 + 本次目标 + 约束红线
- 4 项齐全后复述确认 + 列推进步骤,等用户 yes
- 本次目标命中关键词时主动建议叠加关联模板(加 X → safe-add / 部署 → deploy / 修 bug → fix-bug 或 stuck-bug)
参数含修饰符:
快锚定→ 切 B 模式 2 项问(严肃任务自动升回完整)操作前必问→ 锚定后每步等 yes
核心契约:猜项目踩坑成本远大于锚定 30 秒。4 项齐全前禁止 Edit/Write/Bash 修改类工具。
参数: $ARGUMENTS
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 First seen · 25 lines · 0 tokens per session scan A 9514f2074982
anchor is a command published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 29d ago), licensed MIT. It adds 30 tokens to every session and 337 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 commands, from other repositories
go-review
Go code review for idiomatic patterns.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
cost-tracker
Track session costs, understand token spend, and get optimization tips.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.
test
Run all PandaFilter verification steps in order. Stop and report on first failure. This is the required pre-commit gate.