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 branchegit 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/branche)<a href="https://agentmods.dev/skills/naiersaidane/claude-mastery/branche"><img src="https://agentmods.dev/badge/skills/naiersaidane/claude-mastery/branche/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/branche"><img src="https://agentmods.dev/badge/skills/naiersaidane/claude-mastery/branche.svg" alt="Reviewed on agentmods" width="80" 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.00104 | $0.00382 |
| Opus 5 | $0.00052 | $0.00191 |
| Sonnet 5 | $0.00021 | $0.00076 |
| Haiku 4.5 | $0.00010 | $0.00038 |
Grade A, and why
branche 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 12d 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.
What it actually says
/branche
Crée une nouvelle branche à partir de la dernière version de main.
Étapes
-
Bascule sur main et récupère la dernière version :
git checkout main && git pull origin main -
Si
$ARGUMENTSest fourni (ex./branche feat/algorithme-churn) :- Utilise l'argument directement comme nom de branche
- Crée et bascule sur la branche :
git checkout -b <nom-de-branche>
-
Si aucun argument n'est fourni :
- Demande à l'utilisateur le nom de la branche ou une description du travail
- Propose un nom avec un préfixe conventionnel :
feat/oufix/ - Une fois confirmé, crée la branche :
git checkout -b <nom-de-branche>
-
Confirme la création de la branche en exécutant
git branch --show-current
Conventions de nommage des branches
Utilise ces préfixes :
feat/— Nouvelle fonctionnalitéfix/— Correction de bug
Si l'utilisateur fournit un nom sans préfixe, propose d'en ajouter un.
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.
- 12d ago First seen · 36 lines · 104 tokens per session scan A 9316595de60a
branche is a skill published in the GitHub repository naiersaidane/claude-mastery (51 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 382 once invoked, about $0.0005 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
release-prep
Checks that the current branch is ready for a release-please release PR — conventional commit types, version manifest sync, findings-store state, and CI status. Use when preparing or verifying a release, cutting a release PR, or confirming a branch is safe to merge for release.
datalad
Retrieve, version, and publish scientific datasets with DataLad and git-annex, and capture computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink or a…
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
history-portability
Import Claude Code or Codex history and move complete CCAM datasets between machines. Use when rescanning provider history, importing a copied directory, uploading JSONL or archives, exporting a backup, restoring it idempotently, or verifying that tokens, workflows, runs, rules, and pricing survived.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.