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/a-lottes/aspark/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.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 | $0.00340 | $0.00340 |
| Opus 5 | $0.00170 | $0.00170 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
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 5d 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.
What it actually says
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.
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.
- 5d 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 (19 stars, last pushed 4d ago), licensed MIT. It adds 340 tokens to every session, about $0.0017 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-30.
Other instructions, from other repositories
pocketto AGENTS.md
AGENTS.md instructions for rfxlamia/pocketto, a project described as: A middleweight workflow for serious AI-coded features: less ceremony than BMAD, more accountability than Superpowers. Source : Trust Me Bro.
lead-dev-os CLAUDE.md
Instructions for CaptainMe-AI/lead-dev-os, covering claude.md, project, terminology, plugin architecture and repository structure.
obsidian-vfs AGENTS.md
Instructions for otaviof/obsidian-vfs, covering agents.md, project, architecture, build & verification and conventions.
claude-sdlc CLAUDE.md
Claude Code instructions for lantisprime/claude-sdlc, covering claude.md, what this repo is, design intent — read this before "improving" anything, eat your own dog food and hook strictness philosophy.
universal-remote-control CLAUDE.md
Claude Code instructions for sidkandan/universal-remote-control, covering urc — rc bridge + cli-to-cli communication, quick start, development rules, architecture (v3) and communication strategy.
swarms CLAUDE.md
Instructions for DheerG/swarms, a project described as: Achieve extraordinary results with claude code across a variety of tasks.