Borrowing it
Nothing to install: this file belongs to a-lottes/aSPARK. 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/a-lottes/aSPARK/main/CLAUDE.mdgit clone --depth 1 https://github.com/a-lottes/aSPARKWrote 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/a-lottes/aspark/claude-md)<a href="https://agentmods.dev/instructions/a-lottes/aspark/claude-md"><img src="https://agentmods.dev/badge/instructions/a-lottes/aspark/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/a-lottes/aspark/claude-md"><img src="https://agentmods.dev/badge/instructions/a-lottes/aspark/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.02353 | $0.02353 |
| Opus 5.5 | $0.00941 | $0.00941 |
| Sonnet 5.5 | $0.00471 | $0.00471 |
| Haiku 4.5 | $0.00235 | $0.00235 |
Grade A, and why
aSPARK 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 13d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project notes for Claude Code
Patterns worth keeping across SPARK loops, distinct from .spark/constitution.md
(which holds the project's standing principles) — these are working habits.
Refuted-with-finding is a valid ceremony outcome
A verify-only sweep (or any test/verification-only feature) that finds a
documented claim does not hold live should record it as refuted-with-finding,
not silently pass it or fix it inline. Route the finding (verbatim quote,
file:line, cause) to wherever the actual fix belongs — often a later increment,
since a verify-only feature's own fence typically forbids touching the files the
fix would require. A failed acceptance criterion is itself a valid, honest
outcome; grinding to force a "confirmed" verdict defeats the point of verifying
at all. See .spark/graph-gates-verification/evidence.md (issue #8) for the
worked example.
Check branch staleness before committing a new feature's work
Before /increment starts committing, or at the latest before /go-live's
pre-flight, diff the current working branch against its own merge-base with
main. If the branch's prior PR already merged, cut a fresh branch off
origin/main for the new feature before work piles up on the stale one —
don't discover this at the last gate. /go-live for graph-gates-verification
had to resolve this as a surprise; catching it earlier (e.g. at /spark's
resume, or /increment's first commit) avoids the detour.
This recurred. project-kickoff's whole loop ran uncommitted, directly on
local main, which let it drift 8 commits behind origin/main unnoticed —
including a fully merged sibling feature touching 4 of the same files
project-kickoff itself changed. /go-live's pre-flight caught it (a real
3-way merge check, zero conflicts, then rebuilding the release branch off
current origin/main), but only because the rule above was re-checked live
there rather than assumed clean. The sharper fix this second occurrence
argues for: don't work uncommitted on main at all — commit to a real
feature branch at the start of a loop's work (e.g. /story-time's first
write, or /increment's first task), not only when /increment or /go-live
happen to check. A branch that exists from the start can't silently drift
underneath work already sitting on it.
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.
- 13d ago Changed · +23 lines · +285 tokens per session d68e8638ef0e
- 16d ago Changed · +15 lines · +225 tokens per session d23075c3363d
- 28d ago Changed · +34 lines · +534 tokens per session 1649b53979d9
- 1mo ago Changed · +23 lines · +327 tokens per session 48d083f98f5a
- 1mo ago Changed · +13 lines · +216 tokens per session 4c2f2cf797b1
- 1mo ago Changed · +29 lines · +426 tokens per session 1c5ced8ec63f
- 1mo ago First seen · 27 lines · 340 tokens per session scan A 40ebef1aadc7
aSPARK CLAUDE.md is an instructions file published in the GitHub repository a-lottes/aSPARK (24 stars, last pushed today), licensed MIT. It adds 2,353 tokens to every session, about $0.0094 per session on Opus 5.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-30.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.