Borrowing it
Nothing to install: this file belongs to sturlese/stigmergy. 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/sturlese/stigmergy/main/CLAUDE.mdgit clone --depth 1 https://github.com/sturlese/stigmergyWrote 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/sturlese/stigmergy/claude-md)<a href="https://agentmods.dev/instructions/sturlese/stigmergy/claude-md"><img src="https://agentmods.dev/badge/instructions/sturlese/stigmergy/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/sturlese/stigmergy/claude-md"><img src="https://agentmods.dev/badge/instructions/sturlese/stigmergy/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.01254 | $0.01254 |
| Opus 5 | $0.00627 | $0.00627 |
| Sonnet 5 | $0.00251 | $0.00251 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
stigmergy 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 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stigmergy project doctrine
This repository owns the platform. The knowledge repository is a separate Git checkout configured
with STIGMERGY_REPO; it owns current Markdown knowledge and its operational control files.
Read the implementation specification at specs/karpathy-team-wiki.md before changing architecture
or product behavior. Active documentation lives in docs/ARCHITECTURE.md, docs/OPERATIONS.md, and
docs/RESET.md. Code and tests are authoritative when older prose disagrees.
Invariants
- Git and Markdown are current knowledge. Postgres is operational state and a rebuildable index.
- Every adapter produces the same kind-free
CaptureEnvelopebefore queueing. - Original bytes and readable source pages are immutable during ordinary filing and gardening.
- One serialized writer owns every Git mutation and records one commit and one change ledger row.
- ACL policy is shared. A write may never expose narrower evidence to broader readers.
- The librarian owns notes and concepts. Entity files are minimal machine data owned by entity primitives; raw entity files are not ordinary searchable pages.
- No active write state waits for human approval. Supported uncertainty is represented honestly.
- Corpus-health findings are preventable or autonomously repairable; they are not human tasks.
- Product capabilities are available through Slack, MCP, or the backoffice. Installed CLI commands are service, bootstrap, security, index-operation, or local-bridge entry points.
- Every model-backed path is built by
kernel.llmfrom its closed allowlist through the single OpenRouter boundary (spec §4.1). Same-model provider failover is allowed; model fallback and direct Anthropic, OpenAI, or Gemini credentials are not. No new model without updating the allowlist and the specification together. - Comments and docstrings explain only a local non-obvious invariant or mechanism. History and design narration belong in Git and the specification.
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 · 89 lines · 1,254 tokens per session scan A d8da96afea0b
stigmergy CLAUDE.md is an instructions file published in the GitHub repository sturlese/stigmergy (9 stars, last pushed 13d ago), licensed Apache-2.0. It adds 1,254 tokens to every session, about $0.0063 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
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.
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).
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).
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.
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.