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/jared833/claude-code-hooks/freebienpx skills add jared833/claude-code-hooks --skill freebiegit clone --depth 1 https://github.com/jared833/claude-code-hooksWhat 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.00080 | $0.03411 |
| Opus 5 | $0.00040 | $0.01706 |
| Sonnet 5 | $0.00016 | $0.00682 |
| Haiku 4.5 | $0.00008 | $0.00341 |
Grade A, and why
freebie 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 3d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship a freebie
A free tool on jaredhebb.com. The first one was the Claude house rules generator at
/claude-md, shipped 2026-07-21. This is the repeatable version of that.
The tools live under the Free stuff nav dropdown. They are the top of the funnel: someone uses one, it works, and the course is the next thing they see. They are also the most shareable thing on the site, which is the whole reason they are free.
1. Decide whether to build it at all
Answer these before writing anything. If two or more are bad, pick a different tool.
- Who has this problem, and are there more of them than the last tool served? The generator serves people with no CLAUDE.md. The grader serves people who have one and suspect it is bad, which is a bigger group. Prefer the bigger group.
- Is the output shareable? A score, a grade, a file someone posts a screenshot of. A thing that only helps privately does not spread.
- What does it cost to run per use? Zero is the default and the strong preference.
If it needs a model call, price it out against live pricing (load the
claude-apiskill, do not price from memory), and say what a single abusive paste costs, not just the average. Anything with a running cost is deferred behind revenue. Jared settled the spend order on 2026-07-21: official X API access comes first, all day. - Can it be deterministic instead? A template, a lookup, or a rules engine beats a model call: instant, free, no key on a public endpoint, nothing to rate-limit, and no abuse surface. The house rules generator was going to be an API call and is better as prewritten blocks. Reach for the model only when the work is genuine judgment.
- Does it already exist inside Claude Code?
/initalready drafts a CLAUDE.md from a repo. The generator earns its place by doing the part/initcannot infer: standing rules, escalation preferences, hard limits. If Claude Code already does the whole job, do not rebuild it.
Write the answers into the Notion task before building. That is what made the grader task useful months later.
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.
- 3d ago First seen · 231 lines · 80 tokens per session scan A ef15498bf18d
freebie is a skill published in the GitHub repository jared833/claude-code-hooks (2 stars, last pushed 14d ago), licensed MIT. It adds 80 tokens to every session and 3,411 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…