Borrowing it
Nothing to install: this file belongs to LLM-Coding/Semantic-Anchors. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LLM-Coding/Semantic-Anchors/main/CLAUDE.mdgit 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/instructions/llm-coding/semantic-anchors/claude-md)<a href="https://agentmods.dev/instructions/llm-coding/semantic-anchors/claude-md"><img src="https://agentmods.dev/badge/instructions/llm-coding/semantic-anchors/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/llm-coding/semantic-anchors/claude-md"><img src="https://agentmods.dev/badge/instructions/llm-coding/semantic-anchors/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.09357 | $0.09357 |
| Opus 5.5 | $0.03743 | $0.03743 |
| Sonnet 5.5 | $0.01871 | $0.01871 |
| Haiku 4.5 | $0.00936 | $0.00936 |
Grade A, and why
Semantic-Anchors CLAUDE.md 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 731 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Purpose
This repository is a curated catalog of semantic anchors - well-defined terms, methodologies, and frameworks that serve as reference points when communicating with Large Language Models (LLMs). Semantic anchors act as shared vocabulary that triggers specific, contextually rich knowledge domains within an LLM's training data.
Current Status: The repository is undergoing a major redesign to become an interactive, bilingual website with treemap visualization, role-based filtering, and automated contribution workflow.
First-Time Setup
After cloning, activate the shared Git hooks with one command (works on Unix/macOS and Windows Git Bash):
git config core.hooksPath .githooks
This installs the pre-commit hook that automatically syncs skill/ into plugins/semantic-anchors/skills/ on every commit. No other tools are required.
Git Workflow & Fork Setup
Development takes place in the fork until PRD implementation is complete.
Git Remotes:
origin→raifdmueller/Semantic-Anchors(fork for development)upstream→LLM-Coding/Semantic-Anchors(original repository)
Workflow:
- All feature branches are created in the fork (
origin) - PRs are created within the fork for review
- After PRD implementation is complete, changes will be merged back to upstream
- Use
git push origin <branch>for all development work - Use
git fetch upstreamto sync with original repository if needed
Issue References:
- Issues are tracked in upstream repository: https://github.com/LLM-Coding/Semantic-Anchors/issues
- Reference issues in commits:
feat: implement X (#42)
Git Worktrees for Parallel Team Development
When using agent teams, use Git Worktrees to enable true parallel development:
Setup:
# Create worktree directory
mkdir -p ~/projects/Semantic-Anchors-worktrees
# Create worktree for each feature branch
git worktree add ../Semantic-Anchors-worktrees/feature-<name> -b feature/<name>
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.
- 7d ago Changed · +4 lines · +102 tokens per session 27cca1aaabe9
- 19d ago Changed · +2 lines · +250 tokens per session c52dacff5ca2
- 1mo ago First seen · 725 lines · 9,005 tokens per session scan A 63361d4e3a59
Semantic-Anchors CLAUDE.md is an instructions file published in the GitHub repository LLM-Coding/Semantic-Anchors (521 stars, last pushed 3d ago), licensed Apache-2.0. It adds 9,357 tokens to every session, about $0.0374 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.