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 The-AI-Directory-Company/agents-and-skills --skill program-status-reportgit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/program-status-report)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/program-status-report"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/program-status-report/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/the-ai-directory-company/agents-and-skills/program-status-report"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/program-status-report.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.00033 | $0.01533 |
| Opus 5.5 | $0.00013 | $0.00613 |
| Sonnet 5.5 | $0.00007 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
program-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 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Program Status Report
Before you start
Gather the following from the user before writing:
- What program or initiative does this cover? (Name, scope, and target completion date)
- Who is the audience? (Executive leadership, steering committee, cross-functional stakeholders, or the working team)
- What reporting cadence is this? (Weekly, biweekly, monthly — this determines the right level of detail)
- What happened since the last report? (Milestones hit, milestones missed, scope changes, team changes)
- What decisions or escalations are needed? (Blockers that the audience has authority to resolve)
If the user says "just summarize where we are," push back: "A status report that only reports progress is a changelog. What risks, blockers, or decisions does your audience need to act on?"
Status report template
Program header
State the program name, reporting period, overall status (Green/Yellow/Red), report author, and distribution date. The status color must reflect the worst-case workstream, not an average.
Program: Platform Migration | Period: Mar 3-14, 2025
Overall Status: YELLOW | Author: J. Martinez
Distribution: Steering Committee, Eng Leadership
Executive summary
3-5 sentences maximum. Structure as:
- Overall trajectory — Are we on track to hit the program milestone? State the milestone and date.
- Key progress — The 1-2 most significant accomplishments this period.
- Primary risk or blocker — The single biggest threat to the timeline and what is needed to resolve it.
Executives read this section and nothing else. If the report were only these 5 sentences, the audience should still know whether to worry.
Status by workstream
Use a table with one row per workstream. Every row must include:
| Workstream | Owner | Status | Progress this period | Next milestone | Risk |
|---|---|---|---|---|---|
| Data migration | @Lee | GREEN | Migrated 3/5 schemas | Schema 4 by Mar 21 | None |
| API cutover | @Patel | YELLOW | Auth integration delayed 3 days | Auth complete by Mar 18 | Vendor response time — see Risks |
| Frontend rebuild | @Chen | GREEN | Search page shipped | Settings page by Mar 25 | None |
What ships with it
3 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 · 124 lines · 33 tokens per session scan A 14b508d9cdc5
program-status-report is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 1,533 once invoked, about $0.0001 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-03.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
operations
Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.
process-flowchart-designer
Create process flowcharts and workflow diagrams from descriptions, with optimization suggestions and bottleneck identification. Use when mapping processes, designing workflows, or improving operational efficiency.