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 skills add Jed-Tech/spar-kit --skill specify_and_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/specify_and_plan)<a href="https://agentmods.dev/skills/jed-tech/spar-kit/specify_and_plan"><img src="https://agentmods.dev/badge/skills/jed-tech/spar-kit/specify_and_plan/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/skills/jed-tech/spar-kit/specify_and_plan"><img src="https://agentmods.dev/badge/skills/jed-tech/spar-kit/specify_and_plan.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.00121 | $0.01239 |
| Opus 5.5 | $0.00048 | $0.00496 |
| Sonnet 5.5 | $0.00024 | $0.00248 |
| Haiku 4.5 | $0.00012 | $0.00124 |
Grade A, and why
plan-change 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 1mo 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan change
Mandatory first turn
Start by asking — use this wording (or trivially equivalent):
I see you would like to start ideation and planning for a change. Can you provide me with some context or your goals for the change?
If the user already dropped hints in the same thread (e.g. a working title), add at most one short acknowledging clause, then still use the prompt above so goals stay explicit.
Do not create files, do not draft <change-name>_spec.md or plan.md, and do not interrogate for scope, folder name, or success criteria in full — save that for after they reply.
Until scope and change name are confirmed or clearly settled: do not create Docs/<scope>/Specs/<change-name>/ or write <change-name>_spec.md / plan.md. A response that creates files or fabricates spec or Implementation Plan content before that does not follow this skill.
Voice
Be concise, cheerful, and inquisitive — like a helpful teammate, not a form or checklist read aloud.
Convert discussion into durable context and a clear execution plan.
Conversation flow
After the user responds
- Clarify intent and naming (workflow §1): refine
<change-name>as needed through dialogue. - Resolve scope (workflow §2): conversationally confirm
xp_stream|saturation_regen|_Repoif still unclear; only ask what is missing. - Then proceed sequentially through workflow §3 onward (create folder → context → ideate → spec → …). Do not skip ahead (e.g. no
plan.mdbefore<change-name>_spec.mdis stable).
Outputs
Create:
Docs/<scope>/Specs/<change-name>/
<change-name>_spec.md— intent, constraints, decisions (not step-by-step)plan.md(Implementation Plan) — ordered, concrete, verifiable execution steps
Scope must be one of: xp_stream, saturation_regen, _Repo. If unclear, stop and ask.
Workflow
1. Clarify intent and naming
- Understand the goal from discussion; help refine
<change-name>. - Do not create files yet. (See Mandatory first turn and Conversation flow for opener and sequencing.)
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.
- 1mo ago First seen · 167 lines · 121 tokens per session scan A acc000c1bc92
plan-change is a skill published in the GitHub repository Jed-Tech/spar-kit (17 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 121 tokens to every session and 1,239 once invoked, about $0.0005 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 skills, from other repositories
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
embedding-strategies
Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.
ppt-review
Read this skill before the first deck or output quality review, so its criteria are available when the rendered images arrive. Apply the criteria to current officereview structural output and relevant rendered images. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck…
plotly
Interactive scientific and statistical data visualization library for Python. Use when creating charts, plots, or visualizations including scatter plots, line charts, bar charts, heatmaps, 3D plots, geographic maps, statistical distributions, financial charts, and dashboards. Supports both quick visualizations (Plotly…
material-organizer
Organize only the materials the user has already provided or explicitly pointed to. The job is to make messy inputs easier to scan, reuse, archive, or continue from later while preserving source traceability.
seo-crawl
Agent-wide core connector rule: when any connected search console is used, discover its operations with listconnectortools and invoke each selected operation through callconnectortool; naming listsites or an analytics operation without the core invocation is not execution.