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 instructions/spica-engine/spica/atomic-designgit clone --depth 1 https://github.com/spica-engine/spicaWhat 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 | $0.01815 | $0.01815 |
| Opus 5 | $0.00907 | $0.00907 |
| Sonnet 5 | $0.00363 | $0.00363 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
spica atomic-design.instructions.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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 244 lines · 1,815 tokens per session scan A 1035d78502d4
spica atomic-design.instructions.md is an instructions file published in the GitHub repository spica-engine/spica (100 stars, last pushed 8d ago), licensed AGPL-3.0. It adds 1,815 tokens to every session, about $0.0091 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-01.
Other instructions, from other repositories
Kokoro-Engine CLAUDE.md
Instructions for chyinan/Kokoro-Engine, covering claude.md, git 规范, 项目概述, 常用命令 and 安装依赖.
shopathome copilot-instructions.md
Instructions for johnpapa/shopathome, covering copilot instructions — shop at home, language & framework conventions, javascript / typescript, angular (angular-app) and react (react-app).
data-table-filters CLAUDE.md
Instructions for openstatusHQ/data-table-filters, covering claude.md, project overview, monorepo structure (pnpm + turborepo), key commands and database.
Paperlab AGENTS.md
Instructions for NourMtir0722/Paperlab, covering paperlab — for coding agents, integrating paperlab into a project, stage mode — paper as architecture, content types and lighting is data, not an enum.
Silex AGENTS.md
AGENTS.md instructions for silexlabs/Silex, covering agents.md, tech stack, run it locally, building the desktop app and when writing code for silex (editing source).
openbridge-webcomponents docgen.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering doc generator cli, it never edits the original and keep the prompt aligned with the rules.