Borrowing it
Nothing to install: this file belongs to aligundogdu/bite-ai-dietitian. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aligundogdu/bite-ai-dietitian/main/.claude/skills/weekly-retro/SKILL.mdgit clone --depth 1 https://github.com/aligundogdu/bite-ai-dietitianWrote 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/aligundogdu/bite-ai-dietitian/weekly-retro)<a href="https://agentmods.dev/skills/aligundogdu/bite-ai-dietitian/weekly-retro"><img src="https://agentmods.dev/badge/skills/aligundogdu/bite-ai-dietitian/weekly-retro/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/aligundogdu/bite-ai-dietitian/weekly-retro"><img src="https://agentmods.dev/badge/skills/aligundogdu/bite-ai-dietitian/weekly-retro.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.00052 | $0.00486 |
| Opus 5.5 | $0.00021 | $0.00194 |
| Sonnet 5.5 | $0.00010 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
weekly-retro 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 9d 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 retrospective
Write weekly/YYYY-WNN.md. Read the last 7 daily logs, the previous 1-2 retros, GOALS.md, MEASUREMENTS.md.
Structure
- One sentence. The single most important thing about this week, with the numbers.
- Weight. Start, mid-week low (if any), official end, cumulative. Explain the change with the energy check from the
weigh-inskill. Multi-week window table (1 / 2 / 3 / 6 weeks). - Measurements. Table against the last measured week. Mark new lows; call out noise and placement issues instead of celebrating or panicking about 1-2 cm.
- Nutrition table. One row per day: kcal, protein, carbs, fat, fiber, training yes/no. Weekly averages. Compare with last week's averages.
- Protein is a floor: count days at or above target ("5/6").
- Carbs/fat are ceilings with direction: check distribution too. Higher carbs on training days and lower on rest days is the goal; the reverse is worth pointing out.
- Fiber: raise slowly (+3-4 g/week). A sudden jump commonly bloats the belly and inflates the waist reading.
- Training. Sessions done vs. planned, total volume per session, new top loads. The coach or the user's program decides exercises; the retro only reports.
- Three tasks for next week. Concrete and small, tied to the weakest numbers of this week. Not a rewrite of the plan.
- Carried over. Open questions, missing data (e.g. water intake not reported), things to confirm.
Tone
Write like a person, not a dashboard. Short paragraphs, numbers in context, no wall of emoji. Be honest when the pace is below target, and give the reason you still do or don't change the plan. Always compare against at least one previous week; if none exists, say so.
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.
- 9d ago First seen · 26 lines · 52 tokens per session scan A 002d5edfb946
weekly-retro is a skill published in the GitHub repository aligundogdu/bite-ai-dietitian (5 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 486 once invoked, about $0.0002 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-10-19.
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…