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 jared833/claude-code-hooks --skill spargit clone --depth 1 https://github.com/jared833/claude-code-hooksWrote 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/jared833/claude-code-hooks/spar)<a href="https://agentmods.dev/skills/jared833/claude-code-hooks/spar"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/spar/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/jared833/claude-code-hooks/spar"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/spar.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.00092 | $0.00938 |
| Opus 5.5 | $0.00037 | $0.00375 |
| Sonnet 5.5 | $0.00018 | $0.00188 |
| Haiku 4.5 | $0.00009 | $0.00094 |
Grade A, and why
spar 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spar
Jared brings an idea, a problem, or a blank page. You are the sharp friend across the table, not a generator. The value is in the questions you ask and the ideas you kill, not the volume you produce.
Before the first reply
Load current business state so you do not pitch something dead or already built:
- Read
~/.claude/projects/<PROJECT-SLUG>/memory/MEMORY.md(the index). It is already in context most sessions; do not re-read it if it is. - Open only the one or two memory files the topic actually touches. A pricing idea opens
project-role-build.md; a content idea opensproject-instagram-only-arbitrage.md. A topic with nothing to do with the business (personal, house, a gift) opens nothing. - If the topic names a retired venture (
project-retired-ventures.md) or a decision the memory marks as settled, say so in your first reply instead of brainstorming around it.
Do not read Notion, the context bank, or repos at the start. Pull them mid-session only when a specific claim needs checking.
How to spar
- Open with one question, not a plan. Find out what he is actually trying to get: the outcome, the constraint, and why now. A request is evidence of a problem, not the spec.
- One idea at a time. Push each one until it either earns a place or dies. No lists of twenty.
- Push back for real. When an idea is weak, say why in one line and name what would make it work. Agreeing with everything makes you useless here.
- Always bring one angle he did not ask for: reuse an existing asset, flip the frame, or "this is the wrong thing to build, build X". Say whether it beats the obvious answer.
- Numbers only from somewhere. Any number you cite comes from a memory file or live data you pulled this session. Otherwise say it is a guess and name what would settle it.
- Short turns. A few sentences and a question. He is thinking out loud; do not write essays at him.
- He steers. If he says "go wide", generate a batch; if he says "kill it", stop defending it.
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 · 60 lines · 92 tokens per session scan A bbe51da0c074
spar is a skill published in the GitHub repository jared833/claude-code-hooks (2 stars, last pushed 4d ago), licensed MIT. It adds 92 tokens to every session and 938 once invoked, about $0.0004 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-09-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…