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 LLM-Coding/Semantic-Anchors --skill semantic-anchor-onboardinggit clone --depth 1 https://github.com/LLM-Coding/Semantic-AnchorsWrote 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/llm-coding/semantic-anchors/semantic-anchor-onboarding)<a href="https://agentmods.dev/skills/llm-coding/semantic-anchors/semantic-anchor-onboarding"><img src="https://agentmods.dev/badge/skills/llm-coding/semantic-anchors/semantic-anchor-onboarding.svg" alt="Measured on agentmods" 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.00063 | $0.00370 |
| Opus 5 | $0.00032 | $0.00185 |
| Sonnet 5 | $0.00013 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
semantic-anchor-onboarding 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 8d 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
Semantic Anchor Onboarding (deprecated)
This skill has been renamed to semantic-contracts-installer. The repositioning reflects the project's Anchor/Contract/Skill taxonomy (ADR-007): a bare list of anchors is something the model already knows, while a contract (a named composition of anchors plus a project-local template) is the part it cannot guess — so installing contracts is the high-value job.
What to do
Use the semantic-contracts-installer skill instead. It:
- installs Semantic Contracts (renders their templates into the project's instruction file) as the default mode,
- keeps the former anchor-block behavior as a
--anchors-onlysub-mode, - recognises and idempotently overwrites any block this old skill left (same
<!-- semantic-anchors:start/end -->markers), - only installs a Claude SessionStart hook for files Claude Code does not load natively (no hook for
CLAUDE.md), with matcherstartup.
No migration step is required: point your workflow at semantic-contracts-installer and run it; it replaces the existing marker block in place.
This alias will be removed after one release.
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.
- 8d ago First seen · 29 lines · 63 tokens per session scan A 0baa0c974098
semantic-anchor-onboarding is a skill published in the GitHub repository LLM-Coding/Semantic-Anchors (465 stars, last pushed 6d ago), licensed Apache-2.0. It adds 63 tokens to every session and 370 once invoked, about $0.0003 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…