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 actgit 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/act)<a href="https://agentmods.dev/skills/jed-tech/spar-kit/act"><img src="https://agentmods.dev/badge/skills/jed-tech/spar-kit/act/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/act"><img src="https://agentmods.dev/badge/skills/jed-tech/spar-kit/act.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.00062 | $0.00734 |
| Opus 5.5 | $0.00025 | $0.00294 |
| Sonnet 5.5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
implement-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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement change
Execute the plan in plan.md while strictly preserving the intent in <change-name>_spec.md. Work sequentially, validate each step, keep progress updated. Refine or reorder tasks only for correctness; do not change underlying intent without approval. No silent workarounds, no drifting from the spec.
Inputs
Docs/<scope>/Specs/<change-name>/<change-name>_spec.mdDocs/<scope>/Specs/<change-name>/plan.md- Repository code and docs
Outputs
- Code changes that satisfy
<change-name>_spec.md - Updated
plan.mdwith progress - Proposed
<change-name>_spec.mdupdates (for approval only—do not apply without approval)
Workflow
1. Load context
- Read
<change-name>_spec.mdandplan.md - Confirm scope and change folder
- Identify current progress (checked tasks)
2. Execute tasks in order
For each unchecked task:
- Understand the task and affected files
- Implement the change
- Validate (build/run/tests or targeted checks as appropriate)
- Mark the task complete in
plan.md
Proceed sequentially unless reordering is clearly required for correctness.
3. Validation
- Prefer targeted checks when a full build is unnecessary
- Ensure changes align with Success Criteria in
<change-name>_spec.md - Ask the user to test or validate only if the agent cannot run the needed checks
4. Failure handling
If a task fails:
- Fix obvious issues and retry once
- If still failing: stop, explain the blocker, propose next steps, ask how to proceed
Do not introduce workarounds that change intent or degrade quality without approval.
5. Task evolution (allowed)
- Refine wording for clarity
- Split tasks into smaller steps
- Reorder tasks if needed for correctness
Do not alter task intent in a way that would change the spec.
6. Spec change handling
If implementation reveals incorrect assumptions, missing constraints, or a better approach that changes intent:
- Propose the spec update clearly
- Do not implement that divergent path yet
- Wait for user approval
- Update
<change-name>_spec.mdonly after approval
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 · 103 lines · 62 tokens per session scan A a796f891728a
implement-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 62 tokens to every session and 734 once invoked, about $0.0002 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.