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 week-plangit 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/week-plan)<a href="https://agentmods.dev/skills/jared833/claude-code-hooks/week-plan"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/week-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/jared833/claude-code-hooks/week-plan"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/week-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.00087 | $0.02004 |
| Opus 5.5 | $0.00035 | $0.00802 |
| Sonnet 5.5 | $0.00017 | $0.00401 |
| Haiku 4.5 | $0.00009 | $0.00200 |
Grade A, and why
week-plan 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan the week: 3-2-1
Adopted 2026-09-19 from a Kallaway episode (youtube.com/watch?v=lZc30sUfx64), adapted to
what this setup can measure. Jared films, ports the footage over, and /vid-batch cuts it.
This skill only decides WHAT to film. It runs before the shoot.
The mix
Seven videos a week, in three kinds:
- 2 broad. Topic sits at the widest ring below. Meant to bring new eyes (a good one is tens of thousands of views and a jump in followers). Never wider than the broad ring.
- 4 narrow. Topic sits one or two rings inside. Fewer views, but every viewer is the person the offer is for. This is where trust builds.
- 1 chaos. Anything: a format never tried, a topic from outside the rings but inside his range. A cheap experiment that may earn a bucket next week.
Chunking stays as it is now: one shoot still yields several cuts, hook variants and repurposes still fill spare slots. Those inherit the parent's bucket. The 3-2-1 plans the NEW shoots.
The rings (starting hypothesis, the data decides)
Center is the buyer. Audience as of 2026-09-19: small business owners and solo operators.
- Solo operators and owner-run businesses of 1 to 10 people who do the admin themselves.
- Small business owners at any size, any kind of business.
- Anyone running a business who wants to use AI in it. BROAD ceiling: two videos a week live here.
- AI and productivity for work in general. Too wide. Do not post here.
- Business, entrepreneurship, making money. Never. It brings the wrong followers and teaches the algorithm the wrong audience.
Narrow = rings 1 and 2. Broad = ring 3. If the data says the rings are wrong, rewrite them here and say so in the plan, do not quietly drift.
Ideas are filtered, not invented from this: a topic that would not build trust with ring 1 or 2 is dropped even when it would get views. Trades are outside the Role Build target and never the centerpiece of a video here unless Jared says otherwise.
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 · 140 lines · 87 tokens per session scan A a51b1db7b0aa
week-plan is a skill published in the GitHub repository jared833/claude-code-hooks (2 stars, last pushed 4d ago), licensed MIT. It adds 87 tokens to every session and 2,004 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-09-20.
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…