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 skills add fledgeling-co/fledgeling-plugins --skill status-updategit clone --depth 1 https://github.com/fledgeling-co/fledgeling-pluginsWrote 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/fledgeling-co/fledgeling-plugins/status-update)<a href="https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/status-update"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/status-update/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.
<a href="https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/status-update"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/status-update.svg" alt="Reviewed on agentmods" width="80" 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.00193 | $0.02336 |
| Opus 5.5 | $0.00077 | $0.00934 |
| Sonnet 5.5 | $0.00039 | $0.00467 |
| Haiku 4.5 | $0.00019 | $0.00234 |
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 1mo 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status update — the page is the report
A status update written into chat is read once and then scrolls away. The same content as a page is still there tomorrow, and the portfolio dashboard beside it answers the question the chat message never could: how does this project compare to the other twenty-six.
So the deliverable here is two files and a two-line reply, never a wall of prose.
You write one file — <project>/.status/project.json. Everything else is derived from
it by scripts/render.py: the project's own STATUS.html, its row in
~/Dev/.status/portfolio.json, and the portfolio dashboard at ~/Dev/STATUS.html. Deriving
the dashboard row rather than writing it twice is what stops the two files disagreeing, and
drift between them would be invisible until someone read both.
Deliver exactly that. Do not also paste the report into chat, and do not expand this into a
portfolio survey — that belongs to ship-armada:ship-armada.
Protocol
-
Identify the project. Walk up from the working directory to the child of
~/Dev. If you are in~/Devitself, ask which project rather than guessing. -
Read the existing data at
<project>/.status/project.jsonif it is there. You are updating a record, not starting one, and the fields you have no news about keep their previous values. -
Gather the delta from what you already know. This session is the primary source. Top it up cheaply with
git -C <project> log --oneline --since=<the file's updated stamp>andgit -C <project> status --porcelain. Open other files only where you have reason to think a specific field changed. -
Write
<project>/.status/project.json. The full field list is inreferences/data-contract.md; read it before your first write in a project. Every field is optional exceptproject,updatedandverdict, and a field you have no honest value for is left out rather than filled with a zero — the pages render "not reported" and "nobody checked this" as distinct states, and both are more useful than a false zero.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 177 lines · 193 tokens per session scan A 3c0e9b652d68
status-update is a skill published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 193 tokens to every session and 2,336 once invoked, about $0.0008 per session on Opus 5.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-04.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…