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/getklaim/claude-auto-context/extract-rulesnpx skills add getklaim/claude-auto-context --skill extract-rulesgit clone --depth 1 https://github.com/getklaim/claude-auto-contextWrote 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/getklaim/claude-auto-context/extract-rules)<a href="https://agentmods.dev/skills/getklaim/claude-auto-context/extract-rules"><img src="https://agentmods.dev/badge/skills/getklaim/claude-auto-context/extract-rules.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.00031 | $0.01187 |
| Opus 5 | $0.00015 | $0.00593 |
| Sonnet 5 | $0.00006 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade B, and why
extract-rules scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Analyze session data to find implicit conventions, then create glob-scoped rules in `.claude/rules/local/`. How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract Rules
Analyze session data to find implicit conventions, then create glob-scoped rules in .claude/rules/local/.
Rules = "institutional memory" (Boris Cherny). When Claude makes a mistake, the correction becomes a permanent rule so it never repeats.
The Boris Test
For every candidate rule, ask: "Would removing this cause Claude to make mistakes?" If no → don't create it. If yes → create it.
What Belongs in Rules (extract these)
Rules capture what Claude CANNOT discover by reading code, configs, or package.json:
| Category | Example | Why it's a rule |
|---|---|---|
| Past mistake prevention | "Never use enum, always literal unions" | Correction from user, not in any config |
| Non-obvious commands | "Run bun run test:file -- 'glob'" |
Can't guess the flag syntax |
| Prohibitions | "Never touch prod DB directly" | Safety rail, not in code |
| Hidden sequencing | "Refresh auth token before API calls" | Order dependency not obvious from code |
| Convention divergence | "Error handling: Result type, not try-catch" | Project chose non-default pattern |
| Gotchas | "File X re-exports from Y — edit Y, not X" | Non-obvious indirection |
What Does NOT Belong (never create these)
| Bad Rule | Why | What to do instead |
|---|---|---|
| "This project uses TypeScript" | tsconfig.json exists | Nothing — Claude reads it |
| "Tests are in tests/" | Discoverable from directory structure | Nothing |
| "Use ES modules" | package.json type:module | Nothing |
| "Write clean code" | Self-evident, every project wants this | Nothing |
| "The API returns JSON" | Discoverable from reading route handlers | Nothing |
| Code style already enforced by linter | ESLint/Prettier handles it deterministically | Hook, not rule |
| Anything in CLAUDE.md already | Duplication wastes tokens | Reference CLAUDE.md |
| Frequently changing information | Goes stale, causes wrong behavior | Keep in code comments |
Key principle (Anthropic official): "Never send an LLM to do a linter's job." If something can be enforced deterministically (format, lint, type-check), it should be a hook, not a rule.
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.
- 6d ago First seen · 104 lines · 31 tokens per session scan B 60db2e1b46e1
extract-rules is a skill published in the GitHub repository getklaim/claude-auto-context (10 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,187 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.