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 Abilityai/abilities --skill project-statusgit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/project-status)<a href="https://agentmods.dev/skills/abilityai/abilities/project-status"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/project-status/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/abilityai/abilities/project-status"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/project-status.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.00106 | $0.03865 |
| Opus 5.5 | $0.00042 | $0.01546 |
| Sonnet 5.5 | $0.00021 | $0.00773 |
| Haiku 4.5 | $0.00011 | $0.00386 |
Grade A, and why
project-status 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 6d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.project-status v1.4.1 — recent: arguments no longer break the config resolver. Then proceed.
Purpose
One short daily answer to two questions about one managed project: how is it going and when will it be done. The steward (/project-steward) moves the work and escalates; this skill reports, and turns what waits on the operator into Trinity asks. It never dispatches. Its only registry writes are relaying an ended ask (one comment + the needs-operator → active label flip) — the managing agent is the project's sole issue writer, so this stays inside the standard (§2).
Daily, even when quiet. This is an operator-requested heartbeat for one project, so a no-change day still delivers a one-line report ("nothing moved; projected done ") — unlike the steward, which stays silent when nothing changed.
State dependencies
| Source | Location | Read | Write |
|---|---|---|---|
| Convention doc | PROJECT_STANDARD.md (repo root) or fleet/project-standard.md (orchestrator) — §0 is the configuration |
✓ | |
| Epic + tasks | $REGISTRY, label project:<slug>; plus every repo in $MEMBER_REPOS (comma-separated, §0) for member issues |
✓ | relay of an ended ask only |
| Build ledger | <workspace>/plan.md — see Ledger contract |
✓ | ✓ (Status / Evidence cells only, from verified evidence) |
| Steward digest | $STATE_DIR/digests/<today>.md |
✓ | |
| Status history | <workspace>/status/YYYY-MM-DD.md + status/asks.json |
✓ | ✓ |
The workspace is the epic body's ## Workspace field resolved through the standard's §15 resolver — never derived from the slug.
Ledger contract
plan.md is a markdown table with at least these columns (others are free): Step · Issue (owner/repo#N, or blank for work with no issue) · Estimate (d) (working days) · Depends on (comma-separated step ids, or blank) · Status (todo · in-progress · waiting-on-operator · done) · Evidence (merged PR, commit, file — what proves done). The ledger is the project's plan; this skill only ever edits the Status and Evidence cells, from evidence, never from a summary. /build-chain-style chain ledgers already have this shape.
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.
- 6d ago Changed · +1 lines b4d256cdad75
- 7d ago Changed · +24 lines 455bffe63704
- 9d ago First seen · 111 lines · 106 tokens per session scan A a94ef2daf973
project-status is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 106 tokens to every session and 3,865 once invoked, about $0.0004 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-10-08.
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…