Borrowing it
Nothing to install: this file belongs to ai-ecoverse/slicc. 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/ai-ecoverse/slicc/main/CLAUDE.mdgit clone --depth 1 https://github.com/ai-ecoverse/sliccWrote 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/ai-ecoverse/slicc/claude-md)<a href="https://agentmods.dev/instructions/ai-ecoverse/slicc/claude-md"><img src="https://agentmods.dev/badge/instructions/ai-ecoverse/slicc/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.02514 | $0.02514 |
| Opus 5 | $0.01257 | $0.01257 |
| Sonnet 5 | $0.00503 | $0.00503 |
| Haiku 4.5 | $0.00251 | $0.00251 |
Grade A, and why
slicc 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 yesterday.
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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Repo navigation hub. Keep package details in the nearest package CLAUDE.md and fast-changing how-to in docs/.
Module Map
Purposes per package: docs/root-details.md. Per-package internals: each packages/<name>/CLAUDE.md.
- Web / TS:
packages/webapp/,packages/webcomponents/,packages/chrome-extension/,packages/cherry/,packages/spoon/ - Node / cloud:
packages/node-server/,packages/cloudflare-worker/,packages/cloud-core/,packages/shared-ts/,packages/vfs-root/,packages/dev-tools/,packages/assets/ - Native (Swift / iOS / Go):
packages/swift-launcher/,packages/swift-server/,packages/swift-optel/,packages/swift-traysession/,packages/swift-trayfollower/,packages/swift-traykit/,packages/swift-widgetkit/,packages/ios-app/,packages/slicc-cli/,packages/go-optel/
Other top-level: docs/ (long-form docs + screenshots), packages/*/tests/ (Vitest suites), dist/ (generated; do not hand-edit).
Top-Level Commands
npm install # Install dependencies (first time)
npm run build # Production build (all workspaces)
npm run build -w @slicc/webapp # UI-only build (faster for UI changes)
npm run build -w @slicc/chrome-extension # Chrome extension build into dist/extension/
npm run test # Vitest run
npm run typecheck # Browser + Node typecheck
npm run dev # Thin /cdp bridge + Chrome (UI from hosted origin)
Runtime-specific guides: webapp · cherry · chrome-extension · cloudflare-worker · node-server · cloud-core · shared-ts · webcomponents · spoon · vfs-root · go-optel · swift-launcher · swift-optel · swift-server · swift-traysession · swift-trayfollower · swift-traykit · swift-widgetkit · ios-app · slicc-cli · dev-tools · docs
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.
- yesterday First seen · 136 lines · 2,514 tokens per session scan A 4bbc528194a1
slicc CLAUDE.md is an instructions file published in the GitHub repository ai-ecoverse/slicc (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,514 tokens to every session, about $0.0126 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-09-05.
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.