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 ClarentCinematics/Codex-Skills-for-Enterprise --skill project-status-briefgit clone --depth 1 https://github.com/ClarentCinematics/Codex-Skills-for-EnterpriseWrote 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/clarentcinematics/codex-skills-for-enterprise/project-status-brief)<a href="https://agentmods.dev/skills/clarentcinematics/codex-skills-for-enterprise/project-status-brief"><img src="https://agentmods.dev/badge/skills/clarentcinematics/codex-skills-for-enterprise/project-status-brief/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/clarentcinematics/codex-skills-for-enterprise/project-status-brief"><img src="https://agentmods.dev/badge/skills/clarentcinematics/codex-skills-for-enterprise/project-status-brief.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.00058 | $0.00379 |
| Opus 5.5 | $0.00023 | $0.00152 |
| Sonnet 5.5 | $0.00012 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
project-status-brief 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.
What it actually says
Project Status Brief
Workflow
- Identify project objective, owner, reporting period, current phase, and target milestone.
- Determine health status from evidence: scope, schedule, quality, budget, resourcing, and stakeholder alignment.
- Extract completed work, upcoming milestones, blockers, risks, and dependencies.
- Convert vague activity updates into outcome-focused status language.
- Call out decisions, escalations, or support needed from leadership.
Output Standard
Use this structure by default:
- Status: Green, Yellow, Red, or Unknown with one-sentence rationale.
- Objective: what the project is trying to achieve.
- Progress This Period: outcomes completed, not just activity.
- Milestones: completed, current, and upcoming milestones.
- Blockers / Dependencies: owner, impact, and requested support.
- Risks: risk, probability, impact, mitigation, and trigger.
- Next Actions: owner, action, due date, and success signal.
- Leadership Ask: decision, escalation, or resource request if needed.
Rules
- Use
Unknownwhen health cannot be inferred from the source. - Do not soften material risks to make the update sound better.
- Make escalation asks specific enough that a leader can act.
- Keep the brief suitable for a dashboard, email update, or operating review.
References
Read references/status-patterns.md when the user asks for RAG scoring, dashboard format, or launch-readiness framing.
What ships with it
2 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 · 39 lines · 58 tokens per session scan A cad09432f1f8
project-status-brief is a skill published in the GitHub repository ClarentCinematics/Codex-Skills-for-Enterprise (2 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 379 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
factory
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
factory-collect
Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.