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/analyse/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/analyse)<a href="https://agentmods.dev/skills/socialgouv/egapro/analyse"><img src="https://agentmods.dev/badge/skills/socialgouv/egapro/analyse.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.00048 | $0.01891 |
| Opus 5 | $0.00024 | $0.00945 |
| Sonnet 5 | $0.00010 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
analyse 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analyse
Phase conception de la pipeline. Trois modes auto-détectés :
| Mode | Trigger | Agents invoqués | Sortie |
|---|---|---|---|
| epic | Issue type Feature, ou prompt « nouvelle feature », « parcours », « ajouter une page X » |
product-owner (Opus) → architect (Opus) |
Epic GitHub avec N sous-issues |
| task | Issue type Task, ou prompt « refactor », « migrer », « ajouter un champ X » sans contexte feature |
architect mode task (Opus) |
Commentaire ## Analyse architecte posté sur la task |
| bug | Issue type Bug, ou prompt « bug », « cassé », « ne marche pas », « écart figma », « régression » |
bug-analyst (Opus) |
Commentaire ## Analyse du bug posté sur le bug |
Chaque agent gère lui-même un gate de validation utilisateur explicite avant de poster sur GitHub. L'orchestrateur (toi qui exécutes ce skill) chaîne et ne ré-interroge pas l'utilisateur entre étapes.
Règle absolue : aucun agent conception ne bouge un ticket sur le board. Les transitions To Do → In progress → In review sont la responsabilité de /implement.
Step 0 — Détection du mode
ARG_HEAD="$(echo "$ARGUMENTS" | awk '{print $1}')"
case "$ARG_HEAD" in
'#'[0-9]*|[0-9]*)
ISSUE_N="${ARG_HEAD#\#}"
;;
https://github.com/*/issues/*)
ISSUE_N="$(echo "$ARG_HEAD" | sed -E 's#.*/issues/([0-9]+).*#\1#')"
;;
*)
ISSUE_N=""
;;
esac
EXTRA_CONTEXT="$(echo "$ARGUMENTS" | cut -d' ' -f2-)"
Cas A — issue number fourni
gh issue view "$ISSUE_N" --json number,title,body,issueType,labels,state,comments \
--jq '{number, title, body, issueType: .issueType.name, labels: [.labels[].name], state, comments: [.comments[] | {author: .author.login, body}]}'
Brancher selon issueType.name :
Feature→ mode epic. Si l'issue n'a pas encore de sub-issues +## Analyse PO→ sous-modeepic-create(PO va construire from scratch). Sinon →epic-enrich(PO + architect amendent).Task→ mode task.Bug→ mode bug.- Type absent ou autre → demander explicitement à l'utilisateur quel mode utiliser.
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 · 140 lines · 48 tokens per session scan A bcbbea083f8b
analyse is a skill published in the GitHub repository SocialGouv/egapro (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 1,891 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-09-04.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.