Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/aiming-lab/metaclaw/structured-progress-updatenpx skills add aiming-lab/MetaClaw --skill structured-progress-updategit clone --depth 1 https://github.com/aiming-lab/MetaClawWrote 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/aiming-lab/metaclaw/structured-progress-update)<a href="https://agentmods.dev/skills/aiming-lab/metaclaw/structured-progress-update"><img src="https://agentmods.dev/badge/skills/aiming-lab/metaclaw/structured-progress-update.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 | $0.00043 | $0.00173 |
| Opus 5 | $0.00022 | $0.00086 |
| Sonnet 5 | $0.00009 | $0.00035 |
| Haiku 4.5 | $0.00004 | $0.00017 |
Grade A, and why
structured-progress-update 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 4d 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
Structured Progress Update
When reporting on work in progress, use a consistent structure:
Format:
- Done: List completed items concisely.
- In progress: What is currently being worked on and expected completion.
- Blocked: Any items waiting on external input — state exactly what is needed.
- Next: The immediately next action item.
Principles:
- Be specific:
Completed API integration for /users endpointnotworked on API. - Surface blockers proactively — don't wait to be asked.
- Keep it scannable: bullets over paragraphs.
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.
- 4d ago First seen · 21 lines · 43 tokens per session scan A 0d5b3d306435
structured-progress-update is a skill published in the GitHub repository aiming-lab/MetaClaw (3,494 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 173 once invoked, about $0.0002 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.
Other skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
axolotl
Expert guidance for fine-tuning LLMs with Axolotl - YAML configs, 100+ models, LoRA/QLoRA, DPO/KTO/ORPO/GRPO, multimodal support.
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.
commitment-setup
One-time setup for the commitments tracking system. Creates workspace structure, schema docs, and installs triage and digest missions. Excluded from activation once projects/commitments/README.md exists in the workspace (the file this skill writes as its first step).
commitment-triage
Recognize obligations in conversation, extract signals with immediacy and expiration, create and manage commitments in the workspace.
linear
Linear issue tracker API integration. Covers first-use identity bootstrap (viewer + teams cached), raw GraphQL for list/search/create/update, and the rules for handling "my issues" / "assigned to me" requests.