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 naiersaidane/claude-mastery --skill planifiegit clone --depth 1 https://github.com/naiersaidane/claude-masteryWrote 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/naiersaidane/claude-mastery/planifie)<a href="https://agentmods.dev/skills/naiersaidane/claude-mastery/planifie"><img src="https://agentmods.dev/badge/skills/naiersaidane/claude-mastery/planifie/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/naiersaidane/claude-mastery/planifie"><img src="https://agentmods.dev/badge/skills/naiersaidane/claude-mastery/planifie.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00146 | $0.01124 |
| Opus 5 | $0.00073 | $0.00562 |
| Sonnet 5 | $0.00029 | $0.00225 |
| Haiku 4.5 | $0.00015 | $0.00112 |
Grade A, and why
planifie 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 11d 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.
/planifie
Découpe un PRD en phases indépendamment livrables par tranches verticales (tracer bullets). Sortie dans docs/PLAN.md.
Process
1. Récupère le PRD
Par défaut, lis docs/PRD.md. Si un chemin de fichier est passé en argument, lis-le. Si rien d'utilisable, demande à l'utilisateur de pointer le fichier ou de coller le contenu.
2. Mode extension si PLAN existe
Si docs/PLAN.md existe déjà, lis-le. Repère les user stories du PRD non couvertes par une phase existante et les incohérences avec un PRD qui a bougé. Ne réécris pas les phases déjà validées ; propose des phases additionnelles ou des extensions ciblées, et signale les contradictions à l'utilisateur avant d'écrire.
3. Explore le codebase
Si tu n'as pas déjà exploré le codebase, fais-le pour comprendre l'architecture actuelle, les patterns en place et les couches d'intégration. Si le projet est vierge (greenfield), saute cette étape.
4. Identifie les décisions architecturales durables
Avant de découper, identifie les décisions de haut niveau qui ne devraient pas bouger en cours d'implémentation :
- Structure des routes / patterns d'URL
- Forme du schéma de base de données
- Noms des modèles de données clés
- Approche d'authentification / autorisation
- Frontières des services tiers
Elles vont dans l'en-tête du plan, chaque phase peut s'y référer.
5. Drafte les tranches verticales
Découpe le PRD en phases tracer bullets. Chaque phase est une tranche fine qui traverse TOUTES les couches d'intégration de bout en bout, PAS une tranche horizontale d'une seule couche.
<règles-tranche-verticale>
- Chaque tranche livre un chemin étroit mais COMPLET à travers toutes les couches (schema, API, UI, tests)
- Une tranche terminée est démontrable ou vérifiable seule
- Préfère beaucoup de tranches fines à peu de tranches épaisses
- N'inclus PAS les noms de fichiers, noms de fonctions, ou détails d'implémentation susceptibles de changer
- INCLUS les décisions durables : routes, formes de schéma, noms de modèles </règles-tranche-verticale>
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.
- 11d ago First seen · 124 lines · 146 tokens per session scan A dac6e5d52532
planifie is a skill published in the GitHub repository naiersaidane/claude-mastery (51 stars, last pushed 1mo ago), licensed MIT. It adds 146 tokens to every session and 1,124 once invoked, about $0.0007 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-30.
Other skills, from other repositories
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
atlassian
Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via…
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…