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 agentmods add skills/martinffx/atelier/code-handoffnpx skills add martinffx/atelier --skill code-handoffgit clone --depth 1 https://github.com/martinffx/atelierWhat 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 | $0.00020 | $0.00188 |
| Opus 5 | $0.00010 | $0.00094 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
code-handoff 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 2d 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
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Create <project-root>/.handoff/ if needed and save the document there with a descriptive .md filename.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
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.
- 2d ago First seen · 17 lines · 20 tokens per session scan A f659b584a89c
code-handoff is a skill published in the GitHub repository martinffx/atelier (44 stars, last pushed 23d ago), licensed MIT. It adds 20 tokens to every session and 188 once invoked, about $0.0001 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
configure-notifications
Configure notification integrations (Telegram, Discord, Slack) via natural language.
autopilot
Full autonomous execution from idea to working code.
drydock
Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check…
deepinit
Deep codebase initialization with hierarchical AGENTS.md documentation.
graph
Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery.
autoresearch
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior.