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 Bidiche49/claude-conf --skill handoffgit clone --depth 1 https://github.com/Bidiche49/claude-confWrote 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/bidiche49/claude-conf/handoff)<a href="https://agentmods.dev/skills/bidiche49/claude-conf/handoff"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/handoff.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.00015 | $0.01404 |
| Opus 5 | $0.00008 | $0.00702 |
| Sonnet 5 | $0.00003 | $0.00281 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade B, and why
handoff scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/handoff-system/pending/{SESSION_ID}.txt 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systeme de Handoff - Sauvegarde de Session
Tu es le gestionnaire de handoff. Ta mission est de sauvegarder l'etat complet de la session actuelle et generer un prompt optimise pour continuer dans une nouvelle conversation.
Workflow
0. VERIFIER LA QUESTION EN ATTENTE
IMPORTANT: Avant tout, verifie s'il y a une question utilisateur en attente:
# Lire la question en attente (si existe)
cat ~/.claude/handoff-system/pending/{SESSION_ID}.txt 2>/dev/null
Si un fichier existe, cette question doit etre incluse dans le prompt de continuation car l'utilisateur l'a posee juste avant le handoff et n'a pas eu de reponse.
1. COLLECTER LE CONTEXTE
Analyse la conversation actuelle et extrait:
Informations de base:
- Nom du projet (depuis le chemin de travail)
- Ticket lie (BUG-XXX, FEAT-XXX, IMP-XXX si mentionne)
- Date/heure du handoff
- Objectif principal de la session
Progression:
- Liste des taches completees (avec details)
- Tache en cours (avec etat actuel)
- Taches restantes
- Pourcentage de progression estime
Decisions techniques:
- Choix d'implementation faits
- Raisons de ces choix
- Alternatives ecartees
Fichiers:
- Fichiers crees ou modifies
- Type de modification (creation, edit, suppression)
- Extraits de code cles (si pertinent)
Contexte technique:
- Patterns utilises
- Dependances ajoutees
- Configurations modifiees
- Erreurs rencontrees et solutions
Blocages:
- Problemes non resolus
- Questions en suspens
- Points d'attention
2. GENERER LE FICHIER DE PROGRESSION
Cree le fichier de progression avec un ID unique base sur timestamp:
Emplacement local: .claude-sessions/HANDOFF-{TIMESTAMP}.md
Emplacement global: ~/.claude/handoff-system/sessions/{PROJECT}-{TIMESTAMP}.md
Format du fichier (rempli avec les vraies donnees):
# Session Progress - HANDOFF-{TIMESTAMP}
**Projet:** {nom du projet}
**Date debut:** {estime depuis contexte}
**Date handoff:** {maintenant}
**Ticket lie:** {TICKET-XXX ou "Aucun"}
---
## Objectif de la session
{description claire de ce que l'utilisateur voulait accomplir}
---
## Etat actuel
### Progression globale
{X}% complete
### Ce qui a ete fait
- {tache 1 completee avec details}
- {tache 2 completee avec details}
- ...
### Ce qui reste a faire
- {tache restante 1}
- {tache restante 2}
- ...
---
## Decisions prises
| Decision | Raison | Impact |
|----------|--------|--------|
| {decision 1} | {raison} | {fichiers affectes} |
| {decision 2} | {raison} | {fichiers affectes} |
---
## Fichiers modifies
| Fichier | Type | Statut |
|---------|------|--------|
| `path/to/file1` | Modifie | OK |
| `path/to/file2` | Cree | OK |
---
## Code cle
{uniquement si necessaire pour la reprise}
---
## Blocages / Points d'attention
{liste des problemes ou questions}
---
## Prochaines etapes
1. {action immediate suivante}
2. {action suivante}
3. {action suivante}
---
## Commandes utiles
{commandes bash utiles pour reprendre}
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.
- 7d ago First seen · 221 lines · 15 tokens per session scan B ef815645f6af
handoff is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 1,404 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
tokenhabit
A coaching tool that finds habits in past coding-agent conversations that waste tokens, the text units used to process requests and responses, and suggests ways to reduce that waste.
handoff-update
Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.
ccboard
Launch and navigate the ccboard TUI/Web dashboard for Claude Code. Use when monitoring token usage, tracking costs, browsing sessions, or checking MCP server status across projects.
stacks
Load stack-specific knowledge (conventions, exact lint/test/build commands, common failure patterns) onto the current role agent for the project's detected tech stack(s) — Next.js, React Native, Spring Boot, FastAPI, Django, Rust, etc. Use at the start of any task in an unfamiliar or newly-onboarded repo, or whenever…