Borrowing it
Nothing to install: this file belongs to satanyakiv/NutriSport. 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/satanyakiv/NutriSport/main/.claude/skills/infra-weekly/SKILL.mdgit clone --depth 1 https://github.com/satanyakiv/NutriSportWrote 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/satanyakiv/nutrisport/infra-weekly)<a href="https://agentmods.dev/skills/satanyakiv/nutrisport/infra-weekly"><img src="https://agentmods.dev/badge/skills/satanyakiv/nutrisport/infra-weekly/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/satanyakiv/nutrisport/infra-weekly"><img src="https://agentmods.dev/badge/skills/satanyakiv/nutrisport/infra-weekly.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.00146 | $0.01515 |
| Opus 5.5 | $0.00058 | $0.00606 |
| Sonnet 5.5 | $0.00029 | $0.00303 |
| Haiku 4.5 | $0.00015 | $0.00152 |
Grade A, and why
infra-weekly 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 2mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
infra-weekly — Sunday review of infrastructure portfolio
Drives the weekly review cadence for docs/infrastructure/. The directory exists so portfolio narratives ("how I shipped a KMP app solo in 3 months") are pre-written from real measured wins, not reconstructed from memory under interview pressure. This skill is what makes the weekly cadence actually happen.
When to use
Activate when the user:
- Types
/infra-weeklyor/infra-review - Asks "що ми зробили цього тижня в інфрі?", "тижневий ревʼю", "Sunday review", "weekly infra"
- Mentions wanting to "catch up on infra docs" or "fill in last week's portfolio entries"
- Closes a large infra change and says "let's add this to the portfolio"
Do NOT use for: single-entry additions outside Sunday cadence (just edit the topic file directly per docs/infrastructure/templates/entry.md). The skill is for the weekly sweep, not ad-hoc capture.
Protocol (6 steps, ~15 min)
Step 1 — Scan commits (read-only)
Run:
git log --since="7 days ago" --pretty="%h %s" --all
Note the commit count + SHA range. If the working tree has uncommitted infra changes, include them in the scan via git diff --name-only and git status --short.
Step 2 — Identify infra-touching changes
For each commit, check if any file matches:
.claude/hooks/**.claude/skills/**.claude/rules/**.claude/settings*.json.claude/scripts/**.claude/features/**gradle/libs.versions.tomlbuild-logic/**docs/infrastructure/**(meta-changes to the system itself)
Build a candidate list in chat: "X commits touched infra files; Y look documentable".
Step 3 — Confirm with user
Read the candidate list to user. For each candidate ask: "Document this in <topic>.md? (y/n/skip-and-defer)". Defer reasons: too early to measure, abandoned mid-week, trivial. Deferred items go to "Entries deferred" in WEEKLY_LOG.md.
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.
- 2mo ago First seen · 103 lines · 0 tokens per session scan A c89e766f609e
infra-weekly is a skill published in the GitHub repository satanyakiv/NutriSport (11 stars, last pushed 5mo ago), licensed MIT. It adds 146 tokens to every session and 1,515 once invoked, about $0.0006 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-08-30.
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…