Borrowing it
Nothing to install: this file belongs to matteocervelli/llms. 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/matteocervelli/llms/main/.claude/skills/progress/SKILL.mdgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/progress)<a href="https://agentmods.dev/skills/matteocervelli/llms/progress"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/progress.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.1 | $0.00071 | $0.02010 |
| Opus 5 | $0.00036 | $0.01005 |
| Sonnet 5 | $0.00014 | $0.00402 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade A, and why
progress 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 3d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progress Skill
Purpose
Fills the routing gap that SessionStart leaves open. SessionStart injects data; /progress interprets it and tells you what to do next.
Use mid-session when you've lost track, after a context compaction, or at the start of a new work block.
What it does NOT do: Re-fetch GitHub issues, CHANGELOG, or codebase map — those are already in session context from SessionStart. Running /progress will not flood your context window.
Usage
/progress # current repo only (default)
/progress --all # cross-repo: show recent work from all projects
/progress --no-memory # skip memory recall entirely (fastest, git-only)
No subcommands at v1. One command, one compact output.
Workflow
Step 0 — Memory context (skip if --no-memory)
Run the memory recall command with a hard 10-second timeout. If the command fails, times out, or returns empty or invalid JSON ([], whitespace, non-JSON output), silently skip this step and proceed to Step 1 — this enrichment must never block the rest of /progress.
Default (/progress): scope to current repo only via --project.
With --all: query all repos (omit --project, use --deep --since).
# Detect current repo name (same logic as memory injection hook)
CURRENT_REPO=$(git remote get-url origin 2>/dev/null | sed 's/.*\///' | sed 's/\.git$//')
# Fallback: directory name
CURRENT_REPO=${CURRENT_REPO:-$(basename "$PWD")}
# Compute ISO date for 3 days ago (macOS: date -v-3d, Linux: date -d '3 days ago')
SINCE_DATE=$(date -v-3d +%Y-%m-%d 2>/dev/null || date -d '3 days ago' +%Y-%m-%d 2>/dev/null || echo "")
# Default: scope to current repo
# With --all: cross-repo (drop --project, add --deep --since)
if [[ "$FLAGS" == *"--all"* ]]; then
RECALL_FLAGS="--deep ${SINCE_DATE:+--since "$SINCE_DATE"}"
else
RECALL_FLAGS="--project "$CURRENT_REPO""
fi
timeout 10 uv run --project ~/.claude/skills/memory/recall \
python ~/.claude/skills/memory/recall/scripts/memory_recall.py \
"recent work" $RECALL_FLAGS --compact --limit 5 2>/dev/null
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.
- 3d ago First seen · 167 lines · 71 tokens per session scan A d5ea2b2535d6
progress is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 2,010 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…