Borrowing it
Nothing to install: this file belongs to jkitchin/crucible. 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/jkitchin/crucible/main/CLAUDE.mdgit clone --depth 1 https://github.com/jkitchin/crucibleWrote 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/jkitchin/crucible/claude-md)<a href="https://agentmods.dev/instructions/jkitchin/crucible/claude-md"><img src="https://agentmods.dev/badge/instructions/jkitchin/crucible/claude-md.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.00968 | $0.00968 |
| Opus 5 | $0.00484 | $0.00484 |
| Sonnet 5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
crucible 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crucible: LLM-Compiled Knowledge Base
Overview
Crucible is a personal knowledge base where primary sources are ingested and distilled by an LLM into a structured, interlinked org-mode wiki. The wiki is the LLM's domain; humans rarely edit it directly.
Directory Layout
sources/- Primary source documents, organized by shareability:external/- Copyrighted material (PDFs, web articles). Gitignored.pdfs/- Academic papers, reportsweb/- Web clippings
notebooks/- Your own ELN entries. NOT gitignored.data/- Your own experimental data. NOT gitignored.
wiki/- Distilled org-mode articles. Shareable. Organized by type:concepts/- Concept articles (one topic per file)summaries/- Per-source summariescomparisons/- Cross-source comparison articlesmethods/- Methodology articlesindex.org- Auto-maintained master index
db/crucible.db- Wiki graph database (SQLite). Tracks sources, articles, concepts, and links between them. Regenerable from wiki content.bin/crucible- CLI entry pointsrc/crucible/- Python source code
Conventions
Org-Mode Articles
All wiki articles use org-mode format with scimax conventions:
- Use
#+TITLE:for the article title - Use
#+FILETAGS:for categorization (include article type as a tag) - Use a properties drawer on the top heading with:
:ARTICLE_TYPE:- concept, summary, comparison, or method:SOURCE_KEYS:- space-separated cite keys of primary sources:STATUS:- draft, reviewed, or verified:CREATED:- ISO date
- Use org-ref citations:
cite:key,citep:key,citet:key - Use
[[file:path][description]]links for cross-references between articles - Write in narrative prose, not bulleted lists (unless content demands enumeration)
Ingest Workflow
Ingestion is a two-step process:
- Plan: Read the source, propose articles to create/update, identify concepts and cross-links. Present plan for user approval.
- Write: Execute the approved plan, producing org-mode articles.
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 First seen · 92 lines · 968 tokens per session scan A 457697fd28d9
crucible CLAUDE.md is an instructions file published in the GitHub repository jkitchin/crucible (10 stars, last pushed 2mo ago), licensed MIT. It adds 968 tokens to every session, about $0.0048 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.