frontier-mcp: Skill for Claude Code

.agents/skills/claude-handoff/SKILL.md

claude-handoff is a skill for Claude Code, Codex from 51ck/frontier-mcp. It costs 22 tokens per session (280 once invoked), scanned A, a copy of claude-handoff, MIT.

A handoff workflow that starts a fresh background coding agent with a summary of the current conversation. The summary can include the next task and which other skills the new agent should use.

In plain words
What is it for?
Use it to pass ongoing work to a background agent, including a focused task description, references to existing files, and suggested skills.
Why use it?
It lets another agent continue work without making you repeat the whole conversation. It also calls for excluding secrets and avoiding duplicated information already stored in project artifacts.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is 51ck/frontier-mcp's own configuration. It tells Claude Code and Codex how to work on frontier-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything frontier-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 51ck/frontier-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/51ck/frontier-mcp/master/.agents/skills/claude-handoff/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/51ck/frontier-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for claude-handoff

README.md
[![agentmods](https://agentmods.dev/badge/skills/51ck/frontier-mcp/claude-handoff/github.svg)](https://agentmods.dev/skills/51ck/frontier-mcp/claude-handoff)
Your own site
<a href="https://agentmods.dev/skills/51ck/frontier-mcp/claude-handoff"><img src="https://agentmods.dev/badge/skills/51ck/frontier-mcp/claude-handoff/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.

agentmods 80×15 button for claude-handoff

Your own site · 80×15
<a href="https://agentmods.dev/skills/51ck/frontier-mcp/claude-handoff"><img src="https://agentmods.dev/badge/skills/51ck/frontier-mcp/claude-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 280 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00280
Opus 5 $0.00011 $0.00140
Sonnet 5 $0.00004 $0.00056
Haiku 4.5 $0.00002 $0.00028

Measured 3d ago against content hash 6738e8b7c789, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-20, from the pricing page.

Security

Grade A, and why

claude-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 3d 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.

Origin

This is a copy

100% identical to claude-handoff — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/claude-handoff/SKILL.md · 19 lines

What it actually says

Write a handoff summary of the current conversation so a fresh agent can continue the work. Instead of saving it, launch a background agent seeded with the summary as its prompt: claude --bg --name "<descriptive name>" "<handoff summary>". It starts in the current working directory and returns immediately; the user manages it with claude agents.

Always pass -n/--name with a descriptive name (e.g. --name "Fix login bug"); it sets the display name shown in the job list, session picker, and terminal title.

Include a "suggested skills" section in the summary, naming which skills the next agent should call the Skill tool for.

Do not duplicate content already captured in other artifacts (specs, 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, since the summary becomes the agent's prompt.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the summary accordingly.

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 3d ago First seen · 19 lines · 22 tokens per session scan A 6738e8b7c789

Subscribe to this mod's changes

claude-handoff is a skill published in the GitHub repository 51ck/frontier-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 280 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to claude-handoff, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens