NutriSport: Skill for Claude Code

.claude/skills/infra-weekly/SKILL.md

infra-weekly is a skill for Claude Code from satanyakiv/NutriSport. It costs 146 tokens per session (1,515 once invoked), scanned A, original, MIT.

A weekly review process for recording infrastructure work, such as changes to the systems that run an application, in portfolio documents.

In plain words
What is it for?
Reviewing the past seven days of Git commits, finding infrastructure changes, and adding measured results to portfolio documentation.
Why use it?
It turns recent work into notes while the details are still available, instead of relying on memory later.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is satanyakiv/NutriSport's own configuration. It tells Claude Code how to work on NutriSport itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything NutriSport configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/satanyakiv/NutriSport/main/.claude/skills/infra-weekly/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/satanyakiv/NutriSport

Made for: Claude Code.

Wrote 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.

agentmods badge for infra-weekly

README.md
[![agentmods](https://agentmods.dev/badge/skills/satanyakiv/nutrisport/infra-weekly/github.svg)](https://agentmods.dev/skills/satanyakiv/nutrisport/infra-weekly)
Your own site
<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.

agentmods 80×15 button for infra-weekly

Your own site · 80×15
<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>
Per session 146 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,515 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00146 $0.01515
Opus 5 $0.00073 $0.00758
Sonnet 5 $0.00029 $0.00303
Haiku 4.5 $0.00015 $0.00152

Measured 11d ago against content hash c89e766f609e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 11d 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.

.claude/skills/infra-weekly/SKILL.md · 103 lines

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-weekly or /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.toml
  • build-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.

Read the full file on GitHub · 103 lines

Changes

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.

  1. 11d ago First seen · 103 lines · 0 tokens per session scan A c89e766f609e

Subscribe to this mod's changes

infra-weekly is a skill published in the GitHub repository satanyakiv/NutriSport (11 stars, last pushed 3mo ago), licensed MIT. It adds 146 tokens to every session and 1,515 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens