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-insights/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-insights)<a href="https://agentmods.dev/skills/satsilem/ai-workflow-framework/project-insights"><img src="https://agentmods.dev/badge/skills/satsilem/ai-workflow-framework/project-insights.svg" alt="Measured on agentmods" 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.00126 | $0.01809 |
| Opus 5 | $0.00063 | $0.00905 |
| Sonnet 5 | $0.00025 | $0.00362 |
| Haiku 4.5 | $0.00013 | $0.00181 |
Grade A, and why
project-insights 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 8d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Insights — Triage & Archive
Goal
Help the user keep INSIGHTS.md lean and actionable. Check what's been implemented, what's genuinely still open, and what's gone stale — then confirm with the user section by section before making any changes.
Step 1 — Gather context
Read these files in order:
INSIGHTS.mdin the current project directory — the items to triage- Project
CLAUDE.md— to check whether CLAUDE.md gap items have been filled - Global agent CLAUDE.md — to check whether items were promoted there already
- Skills directory listing — to check whether skill candidates/upgrades exist:
ls /
If no global skills directory is configured, skip that check and continue with
project-local evidence.
For **Skill Upgrade** items, go one step further: read the relevant skill's `SKILL.md` briefly to check whether the described improvement is actually present (not just that the skill exists).
For **Automation Ideas** that mention a specific script or alias, check the shell aliases file or the relevant scripts directory.
Also check lightweight docs hygiene signals:
- `.reference/INDEX.md` exists and includes newly promoted files.
- `.reference` docs touched in recent work have updated `Last reviewed`.
- `.reference` metadata includes `Purpose`, `When to use`, `Source of truth`, `Owner`, `Confidence`, `Last reviewed`.
- Reusable docs in `.ai-notes` are flagged as promotion candidates.
---
## Step 2 — Triage each item
Go through every non-archived item in INSIGHTS.md and assign one status:
| Status | Meaning |
|--------|---------|
| ✅ Done | The improvement exists — skill built, CLAUDE.md updated, script implemented, issue resolved |
| ⏳ Open | Not yet implemented, still clearly relevant |
| 📤 Promote to global CLAUDE.md | A project-level CLAUDE.md gap that's universal enough to belong in the global CLAUDE.md |
| 🗑️ Stale | No longer relevant — project direction changed, different approach taken, or won't fix |
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.
- 8d ago First seen · 190 lines · 126 tokens per session scan A 5137a2d95a43
project-insights is a skill published in the GitHub repository satsilem/ai-workflow-framework (2 stars, last pushed 5mo ago), licensed MIT. It adds 126 tokens to every session and 1,809 once invoked, about $0.0006 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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.