Borrowing it
Nothing to install: this file belongs to satsilem/ai-workflow-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/satsilem/ai-workflow-framework/main/.claude/skills/project-health/SKILL.mdgit clone --depth 1 https://github.com/satsilem/ai-workflow-frameworkWrote 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/satsilem/ai-workflow-framework/project-health)<a href="https://agentmods.dev/skills/satsilem/ai-workflow-framework/project-health"><img src="https://agentmods.dev/badge/skills/satsilem/ai-workflow-framework/project-health/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/satsilem/ai-workflow-framework/project-health"><img src="https://agentmods.dev/badge/skills/satsilem/ai-workflow-framework/project-health.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.00065 | $0.01579 |
| Opus 5 | $0.00032 | $0.00790 |
| Sonnet 5 | $0.00013 | $0.00316 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
project-health 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 9d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Health
Run a full health pass across project documentation, workflows, and operational signals.
Output style:
- Show findings first (highest risk first)
- For each phase, ask what to run:
1,2,1,3,all, orskip - Never apply edits until user confirms
Phase 0 — Scope Confirmation
Ask:
- Target scope: docs-only, ops-only, or full health
- Mode: audit-only or audit+apply
- Time window for freshness checks: 7 / 30 / 90 days
If user already specified these, proceed directly.
Phase 1 — Documentation Health
Sub-tasks:
- Link integrity in
SESSION.md,INSIGHTS.md,CLAUDE.md .reference/metadata completeness (Purpose,When to use,Source of truth,Owner,Confidence,Last reviewed)- Freshness drift (
Last reviewedvs chosen time window) INSIGHTS.mdstatus quality (done/open/stale mix and archive hygiene)TODO.mdstructure compliance (open tasks format and done history consistency)
Prompt:
Which documentation checks should run?
1,2,3,4,5 | all | skip
Report:
- Critical issues
- Warnings
- Healthy checks
- Suggested fixes (no edits yet)
Phase 2 — Workflow Health
Sub-tasks:
- Skill naming consistency (
project-*prefix where intended) - Skill trigger clarity (description includes clear "Use when" trigger phrases)
- Skill drift check (overlapping scopes, duplicate responsibilities)
- CLAUDE.md alignment (local vs global guidance conflicts)
- Recurrence hygiene (monthly/quarterly tasks represented in TODO or skill checklists)
Prompt:
Which workflow checks should run?
1,2,3,4,5 | all | skip
Report:
- Conflicts/duplicates found
- Missing triggers or weak descriptions
- Recommended consolidation actions
Phase 3 — Operational Readiness (Project-level)
Sub-tasks:
- Verify runbook discoverability (
.reference/INDEX.mdmatches actual files) - Verify incident learnings promoted (
SESSION.mdkey learnings reflected in CLAUDE/reference where appropriate) - Verify release guardrails documented (confirm before release, change-control rules, rollback notes)
- Verify monitoring hooks exist (health scripts/aliases documented and discoverable)
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.
- 9d ago First seen · 241 lines · 65 tokens per session scan A b8e75bd0da5c
project-health is a skill published in the GitHub repository satsilem/ai-workflow-framework (2 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 1,579 once invoked, about $0.0003 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
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.