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 khalilbenaz/claude-skills-collection --skill handoff-designergit clone --depth 1 https://github.com/khalilbenaz/claude-skills-collectionWrote 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/khalilbenaz/claude-skills-collection/handoff-designer)<a href="https://agentmods.dev/skills/khalilbenaz/claude-skills-collection/handoff-designer"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/handoff-designer/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/khalilbenaz/claude-skills-collection/handoff-designer"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/handoff-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 158 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- medium Output Handling · line 3 Output from one security context is used in another without boundary enforcement. Cross-context output flow can leak sensitive information or escalate privileges across trust boundaries.Fix: Enforce strict context boundaries. Do not pass output from one security domain into another without explicit validation and redaction of sensitive content.
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.00082 | $0.02563 |
| Opus 5 | $0.00041 | $0.01282 |
| Sonnet 5 | $0.00016 | $0.00513 |
| Haiku 4.5 | $0.00008 | $0.00256 |
Grade A, and why
handoff-designer 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.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Handoff Designer
Quand utiliser ce skill
Un handoff est nécessaire dans quatre situations :
| Situation | Signal | Agent cible |
|---|---|---|
| Capability boundary | Outil ou connaissance manquant | Spécialiste équipé |
| Spécialisation | Sous-tâche mieux traitée ailleurs | Agent optimisé |
| Escalation | Risque ou complexité dépassant le seuil | Agent senior / humain |
| Load balancing | Queue saturée | Instance parallèle |
Décision : si l'agent courant peut compléter la tâche avec une qualité ≥ 80 % sans outil supplémentaire, ne pas handoff — le coût de transition n'est pas justifié.
Workflow en étapes
1. Évaluer le déclenchement
from enum import Enum
class HandoffReason(Enum):
CAPABILITY_BOUNDARY = "capability_boundary"
SPECIALIZATION = "specialization"
ESCALATION = "escalation"
LOAD_BALANCING = "load_balancing"
def should_handoff(task: dict, agent_caps: list[str]) -> tuple[bool, HandoffReason | None]:
missing = [c for c in task.get("required_capabilities", []) if c not in agent_caps]
if missing:
return True, HandoffReason.CAPABILITY_BOUNDARY
if task.get("risk_level", 0) > 7:
return True, HandoffReason.ESCALATION
return False, None
Critères de seuil recommandés : risk_level > 7, complexity_score > 8, sentiment_score < 0.3.
2. Packager le contexte (≤ 2 000 tokens)
Contenu obligatoire du HandoffContext :
from dataclasses import dataclass, field
from typing import Any
import uuid
@dataclass
class HandoffContext:
correlation_id: str # inchangé sur toute la chaîne
source_agent: str
target_agent: str
handoff_reason: str
conversation_summary: str # 5–10 phrases max
user_intent: str # reformulé explicitement
key_facts: dict[str, Any] # entités, montants, références
task_progress: dict # {"step": 3, "total": 7, "completed": [...]}
user_preferences: dict # langue, ton, contraintes détectées
context_ref: str # clé du snapshot complet dans le state store
hop_count: int = 0
handoff_chain: list[str] = field(default_factory=list)
def package_context(history: list, source: str, target: str, reason: str) -> HandoffContext:
summary = summarize_conversation(history) # appel LLM interne
facts = extract_key_facts(history)
ref = store_context_snapshot(history) # Redis / DynamoDB / mémoire partagée
return HandoffContext(
correlation_id=str(uuid.uuid4()),
source_agent=source, target_agent=target,
handoff_reason=reason,
conversation_summary=summary,
user_intent=detect_intent(history),
key_facts=facts,
task_progress={},
user_preferences={},
context_ref=ref,
handoff_chain=[source],
)
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 · 258 lines · 82 tokens per session scan A 1b7b569aa289
handoff-designer is a skill published in the GitHub repository khalilbenaz/claude-skills-collection (22 stars, last pushed 18d ago), licensed MIT. It adds 82 tokens to every session and 2,563 once invoked, about $0.0004 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
explain
Explains code/architecture with Mermaid diagrams and sequence flows. Triggers: what does X do, how does Y work, explain code, sequence diagram.
common-sense-index-investing-bogle
Apply John Bogle index investing rules for low-cost funds, asset allocation, fees, taxes, ETFs, advisers, and buy-hold discipline.
finance-econ-literacy
A Korean-language guide to understanding economic indicators such as interest rates, exchange rates, inflation, GDP, employment, and trade. It explains how these figures can affect loans, savings, investments, and spending.
stock-analysis-lead
Orchestrate a US-stock investment analysis — classify sector archetype, fetch SEC filings, dispatch a tiered fan-out of six vertical equity-research agents (business model, earnings quality, balance sheet, management, industry, peer comparison) over a validated JSON findings contract, then synthesize a buy/hold/sell…
stock-business-review
Review a US-listed company's business model and revenue structure for an equity-research workup. Covers product/service mix, customer concentration, geographic exposure, industry position, revenue-growth decomposition (organic vs acquired vs price vs volume), and information-tier discipline (which numbers are facts vs…
stock-earnings-quality-review
Review a US-listed company's earnings quality, cash-flow integrity, and operating leverage for an equity-research workup. Covers operating cash flow vs net income drift, free cash flow trajectory, capex character (maintenance vs expansion), equity issuance / shareholder-return yield, revenue-quality signals…