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/anentrypoint/freddie/weekly-reviewnpx skills add AnEntrypoint/freddie --skill weekly-reviewgit clone --depth 1 https://github.com/AnEntrypoint/freddieWrote 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/anentrypoint/freddie/weekly-review)<a href="https://agentmods.dev/skills/anentrypoint/freddie/weekly-review"><img src="https://agentmods.dev/badge/skills/anentrypoint/freddie/weekly-review.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00557 |
| Opus 5 | $0.00011 | $0.00279 |
| Sonnet 5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
weekly-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 5d 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.
What it actually says
Weekly Review
Facilitate a structured weekly review. Surface what matters, clear blockers, align on priorities.
Review structure (45 minutes)
1. SHIPPED THIS WEEK (10 min)
Format: [scope] description — impact
Example: [checkout] Reduced p95 latency 800ms → 210ms — unblocks Q2 KR1.1
2. IN PROGRESS (5 min)
State + estimated completion date. Flag anything >50% over estimate.
3. BLOCKERS (10 min)
For each: what is blocked, who can unblock it, ETA. Escalate anything blocked >2 days without a clear owner.
4. DECISIONS NEEDED (10 min)
Format: [decision] options + recommendation + owner + deadline
5. NEXT WEEK PRIORITIES (10 min)
Top 3-5 items, ranked by impact, with an owner.
Output format
WEEKLY REVIEW — Week of 2026-04-28
SHIPPED
✓ [auth] Migrated session storage to Redis — reduces DB load 40%
✓ [infra] Upgraded k8s cluster to 1.29 — zero downtime
IN PROGRESS
→ [checkout] Payment provider migration — 60% done, ETA 2026-05-05
→ [data] ETL pipeline — blocked (see blockers)
BLOCKERS
⚠ ETL pipeline needs Snowflake credentials — owner: @alice, ETA: 2026-05-02
⚠ Design review for onboarding — waiting on design since 2026-04-25
DECISIONS NEEDED
? Monorepo vs multi-repo for mobile — recommend monorepo — owner: @bob — deadline: 2026-05-03
NEXT WEEK
1. Finish payment provider migration — @carol
2. Unblock ETL pipeline — @dave
3. Ship onboarding v2 to 10% of new signups — @eve
Rules
- Shipped items: completed/shipped/merged only — no "worked on X".
- Blockers must have an owner and deadline, or they are risks not blockers.
- Decisions without a deadline are discussions not decisions.
- Next week: ≤5 priorities. Help rank and drop if the team lists more.
- Carry unresolved blockers from last week to the top of this week's list.
Paste last week's notes, Jira/Linear export, or describe what happened and I will produce the review.
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.
- 5d ago First seen · 65 lines · 22 tokens per session scan A 7b50a51a50e4
weekly-review is a skill published in the GitHub repository AnEntrypoint/freddie (0 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 557 once invoked, about $0.0001 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.
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…