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/weigh-in/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/weigh-in)<a href="https://agentmods.dev/skills/aligundogdu/bite-ai-dietitian/weigh-in"><img src="https://agentmods.dev/badge/skills/aligundogdu/bite-ai-dietitian/weigh-in/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/weigh-in"><img src="https://agentmods.dev/badge/skills/aligundogdu/bite-ai-dietitian/weigh-in.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.00048 | $0.00574 |
| Opus 5.5 | $0.00019 | $0.00230 |
| Sonnet 5.5 | $0.00010 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
weigh-in 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.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weigh-in
1. Record
- Weight →
GOALS.mdweigh-in table (date, kg, one-line context: last day's carbs, salt, training, water, sleep). - Tape measurements →
MEASUREMENTS.md(private). Never to bite/. - If the user uses the weight chart in bite/, append only
{week, kg, date, month}tobite/src/data/weight.jsonfor the official weekly weigh-in. Nothing else goes there.
2. Read the number honestly
- One week is noise. Always compute 1, 2, 3 and 6-week windows (kg change and kg/week) and put them in a small table. Decide on the 2-3 week windows, not on this morning.
- Energy check. Average intake of the last 7 days vs. estimated TDEE → expected fat change (≈7,700 kcal per kg). If the scale moved far more than that in either direction, the difference is water or gut content, not fat. Say so with the arithmetic.
- Usual water sources: carbs back up after a low-carb stretch (each g of glycogen holds ~3 g water), a hard or high-volume training session in the last 48 h, salty dinner the night before, low water intake, constipation, a large fibre jump.
- Scale flat, tape down = still losing. A common pattern: the scale stalls for 1-2 weeks while measurements drop, then a "whoosh" catches up. Point to the archive if it has happened before.
- Mid-week low vs. official weigh-in. If the user saw a lower number mid-week, the true floor is usually between the two.
3. Measurements
- Tape noise is ±1-2 cm. One week's change under 2 cm is not a finding.
- If two neighbouring sites suddenly read almost the same (e.g. waist ≈ belly), suspect tape placement before biology. Remind the user of the fixed landmarks in
MEASUREMENTS.md. - Trust direction across 3-4 sites and 3-4 weeks, not a single site.
4. Calibration
Follow the calorie calibration protocol in CLAUDE.md. Small moves only (100-200 kcal), only when the 2-3 week window disagrees with the energy math and measurements are not moving either. Log every change in the GOALS.md calibration table with the reason.
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 · 31 lines · 48 tokens per session scan A 6cefe2a4c7ed
weigh-in is a skill published in the GitHub repository aligundogdu/bite-ai-dietitian (5 stars, last pushed 9d ago), licensed MIT. It adds 48 tokens to every session and 574 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…