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 MarcoZorn/agencykit --skill agency-statusgit clone --depth 1 https://github.com/MarcoZorn/agencykitWrote 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/marcozorn/agencykit/agency-status)<a href="https://agentmods.dev/skills/marcozorn/agencykit/agency-status"><img src="https://agentmods.dev/badge/skills/marcozorn/agencykit/agency-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/marcozorn/agencykit/agency-status"><img src="https://agentmods.dev/badge/skills/marcozorn/agencykit/agency-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.00036 | $0.02250 |
| Opus 5 | $0.00018 | $0.01125 |
| Sonnet 5 | $0.00007 | $0.00450 |
| Haiku 4.5 | $0.00004 | $0.00225 |
Grade A, and why
agency-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 12d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agency Status
When to use this skill
English: "status update", "team briefing", "weekly update", "what's happening", "Monday briefing", "agency status".
Italiano: "stato agenzia", "briefing team", "aggiornamento settimanale", "riunione lunedì", "come stiamo".
What this skill does
Gives an agency owner or PM a single, honest read of the whole studio in thirty seconds: every active project on a traffic light, the three things that actually matter this week, what is blocked and who unblocks it, and a briefing message ready to drop in Slack or WhatsApp on Monday morning. It replaces the vague "how's everything going" with a picture you can act on.
Inputs required
- The active projects — names and, for each, a line on where it stands.
- Deadlines coming up this week or next.
- Anything stuck — waiting on a client, a person, an asset, a payment.
- The team — who owns what, so blockers get a name attached.
If the user dumps everything unstructured, sort it yourself. If a project has no clear owner or next step, that absence is itself a finding — surface it.
Output format
- PROJECT STATUS — traffic-light per project with a one-line reason.
- TOP 3 PRIORITIES — what the week turns on.
- BLOCKED — each blocker with owner and the single next action.
- MORNING BRIEFING — Slack/WhatsApp-ready message, copy-paste as-is.
Brand voice
If a BRAND.md file exists in this skill's folder (.claude/skills/agency-status/BRAND.md) or in .claude/brand/BRAND.md (global fallback), read it before generating output and apply its tone, terminology, and examples to all text you produce. A skill-local BRAND.md overrides the global one; if neither exists, use a clean, professional default voice.
Instructions
1. Traffic-light every project
Assign each project a status and one line explaining it:
- 🟢 On track — moving, no help needed, deadline safe.
- 🟡 At risk — a deadline is tight, feedback is slow, or a dependency is wobbling. Not on fire yet, but watch it.
- 🔴 Blocked — cannot progress without a specific unblock.
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.
- 12d ago First seen · 182 lines · 36 tokens per session scan A c18d2e0d2652
agency-status is a skill published in the GitHub repository MarcoZorn/agencykit (6 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 2,250 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-31.
Other skills, from other repositories
run-operational-review
Use when facilitating a recurring business review meeting to assess operational performance, address blockers, and align leadership on priorities.
workflow-run
Use when you need to execute a DAG-structured workflow template from SKILLS/ORCHESTRATION FRAMEWORK/workflow-templates/.
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
omh-agent-board
This is a Hermes-native agent-board workflow skill.
omh-research-department
This is a Hermes-native research-department workflow skill.
omh-cto-loop
This is a Hermes-native cto-loop workflow skill.