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 flurdy/agent-skills --skill peer-sessiongit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/peer-session)<a href="https://agentmods.dev/skills/flurdy/agent-skills/peer-session"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/peer-session/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/flurdy/agent-skills/peer-session"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/peer-session.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.04393 |
| Opus 5.5 | $0.00018 | $0.01757 |
| Sonnet 5.5 | $0.00009 | $0.00879 |
| Haiku 4.5 | $0.00005 | $0.00439 |
Grade A, and why
peer-session 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 4d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Peer session
One human-approved request to an existing live peer. Use when another session has project context or machine-local access the caller lacks. This is a thin workflow over Claude Code's native cross-session tools or orca-cli, not another terminal API, inbox, supervisor or task tracker.
Intent and dependencies
/peer-session ask <peer/project> <question> # Claude Code
/peer-session tell <peer/project> <instruction> # response optional
/skill:peer-session ask <peer/project> <question> # Pi
ask waits within a fixed budget for an answer. tell returns send evidence without
waiting for an answer or completion. Omitted/unclear intent or recipient needs one
clarifying question; never choose another task from tracker text. A fresh invocation
handles one request, not a conversation loop.
For Orca, load the installed orca-cli skill from the runtime's available skills. It owns executable selection, platform hazards, version-matched guide loading, selectors, terminal commands, receipt/recovery syntax and capability discovery. Reuse its exact resolved executable throughout. Do not modify or install that externally owned skill, copy its command reference here, guess unsupported flags or switch executables after failure. If the skill, CLI or required runtime capability is unavailable, report the exact missing dependency/error and stop without installing or opening anything.
An Orca caller needs a running Orca runtime that can discover the recipient. Different Orca windows/instances are not assumed to share inventory. A remote SSH workspace inside the caller's Orca runtime is distinct from another machine's independent Orca instance. Use only already configured routes; do not pair environments or alter SSH configuration here. Receipt retrieval additionally needs an authorized local read or an already authenticated, host-key-verified remote read route.
Full ownership handoffs belong to orca-cli. Supervised Tasks, Dispatches, Run inboxes and ask/reply gates belong to Orca's orchestration guide. Native delegated children belong to delegate-work. Do not enter any of those workflows automatically or use this skill to bypass a failed delegation lane.
What ships with it
2 files 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.
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.
- 4d ago Changed · +1 lines 349e470c2046
- 6d ago Changed · +143 lines · +7 tokens per session 356868aa07ea
- 28d ago First seen · 203 lines · 38 tokens per session scan A 0c7d351b602c
peer-session is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 4,393 once invoked, about $0.0002 per session on Opus 5.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-09-22.
Other skills, from other repositories
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…
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…
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.
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…