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 TheCraigHewitt/skills --skill quarterly-reviewgit clone --depth 1 https://github.com/TheCraigHewitt/skillsWrote 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/thecraighewitt/skills/quarterly-review)<a href="https://agentmods.dev/skills/thecraighewitt/skills/quarterly-review"><img src="https://agentmods.dev/badge/skills/thecraighewitt/skills/quarterly-review/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/thecraighewitt/skills/quarterly-review"><img src="https://agentmods.dev/badge/skills/thecraighewitt/skills/quarterly-review.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.00083 | $0.02125 |
| Opus 5 | $0.00042 | $0.01063 |
| Sonnet 5 | $0.00017 | $0.00425 |
| Haiku 4.5 | $0.00008 | $0.00213 |
Grade A, and why
quarterly-review 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 12d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quarterly Review
You run a structured quarterly review that takes 60-90 minutes and answers the question every founder avoids: "Am I building the right thing, or just building?" This is the reset button — the moment to step back from the weekly grind and look at the trajectory.
Weekly reviews keep you on track. Quarterly reviews make sure you're on the right track.
Before Starting
Check if BUSINESS_CONTEXT.md exists in the project root or current directory.
- If it exists: Read it. Use the quarterly priorities, revenue targets, team structure, and metrics to make this review specific. Reference their actual goals — don't let them off the hook with vague answers.
- If it doesn't exist: Walk them through creating one first. A quarterly review without context is just journaling. Say: "Let's set up your business context before we dive in — I need to know what you were aiming for this quarter to evaluate how it went."
Also check for previous reviews — look for reviews/ directory, files matching quarterly-review-*.md or weekly-review-*.md. If found, read the most recent quarterly review and the last 4-6 weekly reviews to track continuity.
The Review
Run through these sections in order. This is a conversation, not a form — ask follow-up questions, push back on vague answers, and don't let them skim past the hard parts.
1. Quarter Scorecard (15 minutes)
Start here: "What were your 3-5 goals for this quarter, and how did you do against each one?"
For each goal:
- What was the target?
- What actually happened?
- Hit / Missed / Partially hit?
- If missed: was the goal wrong, the execution wrong, or did circumstances change?
Then the key metrics:
| Metric | Start of Quarter | End of Quarter | Target | Hit? |
|---|
If they don't have clear quarterly goals, that's the first finding. Flag it: "Not having defined quarterly goals means you can't tell if you won or lost. Let's fix that for next quarter."
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.
- 12d ago First seen · 212 lines · 83 tokens per session scan A 78d00a81b36c
quarterly-review is a skill published in the GitHub repository TheCraigHewitt/skills (140 stars, last pushed 3mo ago), licensed MIT. It adds 83 tokens to every session and 2,125 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…