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 skills/a-lottes/aspark/sparknpx skills add a-lottes/aSPARK --skill sparkgit 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/skills/a-lottes/aspark/spark)<a href="https://agentmods.dev/skills/a-lottes/aspark/spark"><img src="https://agentmods.dev/badge/skills/a-lottes/aspark/spark.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.00073 | $0.01827 |
| Opus 5 | $0.00036 | $0.00914 |
| Sonnet 5 | $0.00015 | $0.00365 |
| Haiku 4.5 | $0.00007 | $0.00183 |
Grade A, and why
spark 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spark — The Full Loop (Orchestrator)
You are conducting the entire SPARK loop for one feature. You don't do the phase work yourself — each ceremony's skill defines it. You sequence the ceremonies, enforce the gates, and keep the user in charge at every transition.
Input
- With an idea as argument → start a fresh loop at Specify.
- Without an argument → resume: pick the feature (single one in
.spark/→ use it; several → ask the user), read its artifacts' statuses, and continue at the first phase whose gate is not yet closed (see the phase map below). - Without an argument, and no feature to resume (every existing feature
is
released, or.spark/is empty) → don't guess an idea. Tell the user there's nothing to resume and offer/next-stepsto have the Product Owner propose one from the project's current state, or ask them to bring their own idea.
The Phase Map
Determine the current position from artifact statuses in
.spark/<feature-name>/ — from the statuses, not the artifacts. What
places the loop is the Status row in each file's header table plus the
Status column of the task table in plan.md. Grep for those or read the
first few lines; a resume that reads a whole spec and plan to answer "which
phase am I in" spends thousands of tokens on a five-line question, and it
spends them in the context the rest of the loop still has to fit into.
| Artifact state | Next ceremony |
|---|---|
no spec.md |
/story-time |
spec.md is draft, UI-facing, design review empty |
/look-and-feel |
spec.md is draft otherwise |
finish /story-time (approval) |
spec.md approved, no/unapproved plan.md |
/sprint-plan |
plan.md approved, tasks not all done |
/increment |
tasks done, review.md missing or not passed |
/peer-review |
review.md passed, qa.md missing or not passed |
/demo-day |
review.md + qa.md passed, no released/handed-off release |
/go-live |
release released |
loop closed — tell the user |
release handed-off |
loop closed for this team — tell the user it's handed off, not yet approved elsewhere |
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 Changed · +12 lines e5e6122b8710
- 5d ago First seen · 117 lines · 73 tokens per session scan A 1f3e36e69540
spark is a skill published in the GitHub repository a-lottes/aSPARK (19 stars, last pushed 4d ago), licensed MIT. It adds 73 tokens to every session and 1,827 once invoked, about $0.0004 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 skills, from other repositories
audit-context
Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.
agentic-workflow-audit
Use when reviewing or auditing an existing agent / LLM-pipeline architecture — e.g. 'is my workflow actually decomposed or secretly a mega-agent?', 'are my task boundaries and success criteria right?' — even without the word 'audit'. ｜ 要檢視／review／稽核既有 agent 或 LLM pipeline 的架構，或問「有沒有拆好」「是不是變成 mega agent」「task…
writing-mode
Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.
triage-mode
Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.
citation-receipts
Systematic per-citation verification protocol for academic writing. MUST be used whenever writing content that cites sources — papers, blog posts, SOTAs, or any document making factual claims about external work. Triggers (FR + EN) on any writing task involving references, citations, or bibliographic claims, or when…
sota-writer
Write structured State-of-the-Art (SOTA) reviews / literature reviews for academic research projects with zero hallucinated citations. Activate this skill whenever the user wants to write, update, or expand a SOTA. Triggers (FR + EN) : "écris un SOTA", "état de l'art sur", "revue de littérature", "mise à jour SOTA"…