status-update

status-update is a skill for Claude Code, Codex from etrebels/claude-code-growth-os. It costs 41 tokens per session (131 once invoked), scanned A, original, MIT.

A short update built from recent daily work-log entries, organized around what moved, what is blocked, and what comes next.

In plain words
What is it for?
Use it to prepare a team, weekly, or board update of fewer than 120 words, with an option to save it as a dated update file.
Why use it?
It turns scattered notes into a concise message that a busy manager, team, or board can understand quickly. It keeps the focus on outcomes rather than activity.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/etrebels/claude-code-growth-os/status-update
Any agent
npx skills add etrebels/claude-code-growth-os --skill status-update
Clone the repo
git clone --depth 1 https://github.com/etrebels/claude-code-growth-os

Made for: Claude Code, Codex.

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 status-update

README.md
[![agentmods](https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/status-update.svg)](https://agentmods.dev/skills/etrebels/claude-code-growth-os/status-update)
Your own site
<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/status-update"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/status-update.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 131 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00041 $0.00131
Opus 5 $0.00020 $0.00066
Sonnet 5 $0.00008 $0.00026
Haiku 4.5 $0.00004 $0.00013

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

Security

Grade A, and why

status-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 5d 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/status-update/SKILL.md · 15 lines

What it actually says

Status Update

Draft a short update a busy stakeholder would actually read, from ops/daily-log.md:

  1. Read the last five to seven entries.
  2. Write three bullets: what moved, what's blocked, what's next.
  3. Keep it under 120 words. Lead with the outcome, not the activity. No filler.

Offer to save it to ops/updates/<date>.md.

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. 5d ago First seen · 15 lines · 41 tokens per session scan A b6fc3fd4ab7f

Subscribe to this mod's changes

status-update is a skill published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 6d ago), licensed MIT. It adds 41 tokens to every session and 131 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.

Related

Other skills, from other repositories

startup-launch-playbook

A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.

Gingiris-1031/gingiris-skills · 58 tokens

plan-devex-review

Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to…

forbotsake/forbotsake · 156 tokens

gstack

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or…

forbotsake/forbotsake · 84 tokens

health

Code quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is the codebase", "run all checks", "quality score". (gstack).

forbotsake/forbotsake · 77 tokens

investigate

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug…

forbotsake/forbotsake · 112 tokens

open-gstack-browser

Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome"…

forbotsake/forbotsake · 107 tokens