Borrowing it
Nothing to install: this file belongs to SpillwaveSolutions/wiki_ticket_sdd. 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/SpillwaveSolutions/wiki_ticket_sdd/main/.claude/skills/status-report/SKILL.mdgit clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sddWrote 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/spillwavesolutions/wiki_ticket_sdd/status-report)<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/status-report"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/status-report.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.00060 | $0.00664 |
| Opus 5 | $0.00030 | $0.00332 |
| Sonnet 5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
status-report 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.
What it actually says
Status report
-
Pick the kind from the ask:
daily(the standup — terse, item-level),weekly(the stakeholder rollup — epic-level), ortimecard(the billing narrative — a sentence or two per day; §17 Q4 is closed: no hours). -
Run
bin/worklog status --kind <kind> --emit-factsand read the JSON. For a timecard, add--since YYYY-MM-DD --until YYYY-MM-DDwhen the ask names a window (default: the last 7 days). Every claim in the report comes from these facts — not from memory of the session. -
Write the prose per §13.3's shapes:
- daily — terse bullets, fits on a screen: Shipped / In flight (with ages — a 9-day-old "in progress" is the whole story) / Blocked (and by what) / Unplanned / Needs attention (conflicts, deferred syncs).
- weekly — prose plus tables grouped by epic: what shipped, slippage (still open despite being in flight at the window start), the unplanned rollup with the percentage of closed items that were unplanned, and what's next.
- timecard — ONE SHORT PARAGRAPH PER DAY: a sentence or two saying
what the day consisted of, in plain language, under a day heading like
## Monday, 14 July. No tables, no ticket IDs in the reading path, no status columns. Days without activity are omitted, not padded.
THE UNPLANNED SECTION IS THE POINT — always include it (in a timecard, as prose in the day's paragraph, never as a percentage).
-
Pipe the prose to
bin/worklog status --kind <kind> --write(timecard: repeat the same--since/--until; the file lands atdocs/status/<until>-timecard.md). Commit the report file, together with the log/roadmap if they were touched. -
Run
bin/worklog triggers status-report. Publish via the wiki-publish skill flow (keystatus/<date>-<kind>; timecard:status/<until-date>-timecard) only ifwiki-publishorwiki-publish:statusis listed. An empty list means write the file and stop — do not publish. Status reports are frozen — publish once, never re-publish.
Never regenerate an existing report (invariant 15.9). If a report was wrong, the correction goes in the next report, not into the old one.
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 Changed 7fd7f83d075c
- 7d ago First seen · 49 lines · 60 tokens per session scan A 5df64fb952a7
status-report is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 664 once invoked, about $0.0003 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.