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/jed-tech/spar-kit/spar-plannpx skills add Jed-Tech/spar-kit --skill spar-plangit clone --depth 1 https://github.com/Jed-Tech/spar-kitWrote 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/jed-tech/spar-kit/spar-plan)<a href="https://agentmods.dev/skills/jed-tech/spar-kit/spar-plan"><img src="https://agentmods.dev/badge/skills/jed-tech/spar-kit/spar-plan.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.00060 | $0.01119 |
| Opus 5 | $0.00030 | $0.00560 |
| Sonnet 5 | $0.00012 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
spar-plan 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 4d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Turn an active spec into a stable implementation plan.
Planning is the bridge between intent and action. Stabilize what must be true before defining how to execute it.
Role
- The user represents product intent and domain context.
- You are the lead engineer for planning: concise, practical, and explicit about tradeoffs.
Use technical judgment, but do not invent product intent. If a choice materially affects scope, success, validation, or risk, surface it clearly with a short recommendation and concrete options. Prefer "I recommend X because..." over open-ended tradeoff dumps, while still letting the user choose.
Inputs
specs/active/<change-name>/<change-name>_spec.md- Optional notes or artifacts in the same folder, such as
research.md - Relevant repository code and documentation
If the active change folder or spec file is missing, stop and use spar-specify first.
Templates
Before completing <change-name>_spec.md, read assets/spec.md and preserve its section order.
Do not create plan.md until the user has explicitly approved the spec for planning.
Before creating plan.md, read assets/plan.md and use it as the template.
Do not create plan.md until the spec is stable enough to support reliable tasks.
Capture Planning Context
Before asking new questions, extract what is already known from the spec, thread, notes, repository files, and docs. Do not make the user repeat context that is already available.
Use repo research to reduce burden on the user when local context can answer a planning question. Preserve optional artifacts in the change folder.
Ask only for gaps that materially affect success criteria, scope, task order, risk, or validation.
Complete the Spec
Refine the spec so it captures durable intent, not step-by-step implementation.
- Keep
Summary,Problem,Scope, andOut of Scopealigned with the user's intent. - Fill
Constraintswith solution requirements that must remain true. - Fill
Success Criteriawith concrete, testable outcomes. - Fill
Decisionswith important product and technical choices that implementation should treat as fixed. - Keep
Open Questionsonly for unresolved questions that materially affect implementation or validation.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 117 lines · 60 tokens per session scan A cd0ecb204561
spar-plan is a skill published in the GitHub repository Jed-Tech/spar-kit (17 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,119 once invoked, about $0.0003 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
vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.
trellis-session-insight
Reach into past AI conversation history through the trellis mem CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work…
kn-init
Use at the start of a new session to read project docs, understand context, and see current state.
trellis-channel
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.