Borrowing it
Nothing to install: this file belongs to SocialGouv/egapro. 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/SocialGouv/egapro/alpha/.claude/skills/report/SKILL.mdgit clone --depth 1 https://github.com/SocialGouv/egaproWrote 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/socialgouv/egapro/report)<a href="https://agentmods.dev/skills/socialgouv/egapro/report"><img src="https://agentmods.dev/badge/skills/socialgouv/egapro/report.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.01391 |
| Opus 5 | $0.00030 | $0.00696 |
| Sonnet 5 | $0.00012 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
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 3d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/report — Dashboard orchestrateur
Usage
/report— dashboard des agents actifs (tous epics confondus)/report <N>— dashboard + état des sous-tickets de l'epic #N/report <N1> <N2> ...— dashboard + état multi-epic
Exécution
Cas nominal — juste le dashboard des agents actifs :
bash scripts/orchestration/render_dashboard.sh
Ce script pur bash lit .claude/state/epic_run/agents/*.log, calcule pour chaque agent son statut (healthy / slow / stuck) via agent_status.sh, son coût LLM (live ou estimate) via compute_cost.sh, et rend une table compacte :
AGENT TICKET PHASE ATTEMPT AGE MODEL EST. $ REASON
Les agents flagués 🔴 stuck déclenchent automatiquement un drill-down (last 20 events, shell command actif, git status du worktree, dernier check CI failed, dernier comment PR) — fourni par agent_drilldown.sh. Les ⚠ slow sont juste mentionnés dans la table sans drill-down.
Cas avec epic(s) en argument — ajouter l'état des sous-tickets :
bash scripts/orchestration/render_dashboard.sh
echo ""
bash scripts/orchestration/epic_state.sh <N1> [<N2> ...]
epic_state.sh affiche un tableau compact : numéro, status board, labels, last_event, age, retries, PR.
Format du rapport
Le dashboard est déjà formaté par les scripts. Tu n'as qu'à :
- Exécuter les commandes bash ci-dessus
- Re-rendre les tableaux en markdown propre (colonnes alignées, headers
|syntax). L'UI utilisateur rend mal les tableaux bash bruts (── boxes, alignement à espaces multiples). - Joindre une analyse : interprétation de l'état actuel, qui bouge, qui est bloqué, prochaine étape attendue.
Note : la version « copier-coller la sortie telle quelle » a été remplacée par cette mouture markdown + analyse. Les scripts bash restent la source de vérité — la donnée vient toujours d'eux, ne pas inventer.
Mode auto-report (lancé depuis /loop, e.g. par /implement)
Quand /report est invoqué via /loop (mode dynamic-pacing), il devient l'élément central d'un suivi automatique pendant la durée d'un /implement epic. À chaque iteration :
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.
- 3d ago First seen · 98 lines · 59 tokens per session scan A af5782a4d383
report is a skill published in the GitHub repository SocialGouv/egapro (12 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 1,391 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-09-04.
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.