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 retaingit 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/retain)<a href="https://agentmods.dev/skills/jed-tech/spar-kit/retain"><img src="https://agentmods.dev/badge/skills/jed-tech/spar-kit/retain/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/retain"><img src="https://agentmods.dev/badge/skills/jed-tech/spar-kit/retain.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.00066 | $0.00624 |
| Opus 5.5 | $0.00026 | $0.00250 |
| Sonnet 5.5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
document-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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document change
Turn completed implementation into clean, accurate, durable knowledge: honest <change-name>_spec.md, captured decisions, broader doc updates only with approval, then archive the change folder.
Inputs
Docs/<scope>/Specs/<change-name>/<change-name>_spec.mdDocs/<scope>/Specs/<change-name>/plan.md- Completed code changes
- Repository documentation (e.g.
README,Docs/technicalBrief.md, setup or usage docs)
Outputs
- Finalized
<change-name>_spec.md(matches actual behavior) - Optional updates to broader docs (after approval)
- Archived folder:
Docs/<scope>/Archive/<change-name>/(contents moved fromSpecs/)
Workflow
1. Review implementation vs spec
- Compare implemented behavior with
<change-name>_spec.md - Note mismatches, missing decisions, outdated assumptions
2. Update <change-name>_spec.md
- Reflect final behavior (spec must match reality, not original guesses)
- Update Decisions, Constraints, Success Criteria as needed
- Resolve or remove stale Open Questions
- Keep intent-focused; no step-by-step implementation in the spec
3. Identify broader documentation impact
- Use Documentation Impact in
<change-name>_spec.mdand the change itself - Consider:
Docs/technicalBrief.md, README, setup/usage, developer notes
4. Propose broader documentation updates
- List suggested edits clearly. Be concise.
- Do not apply until the user approves
5. Apply approved updates
- Update only what was approved; keep changes minimal and accurate
6. Final cleanup
<change-name>_spec.md: clear and completeplan.md: final state (all done or explained); trim noise and temporary notes
7. Archive change
Move the entire folder:
Docs/<scope>/Specs/<change-name>/ → Docs/<scope>/Archive/<change-name>/
(Create Archive if missing.)
Rules
- Spec describes final behavior; not a build log
- No silent edits to README, technical brief, or other repo docs—approval first
- Stay concise
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 · 85 lines · 66 tokens per session scan A b7a881cf419e
document-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 66 tokens to every session and 624 once invoked, about $0.0003 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.