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/kelp/agent-plugins/pairnpx skills add kelp/agent-plugins --skill pairgit clone --depth 1 https://github.com/kelp/agent-pluginsWhat 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.00118 | $0.03224 |
| Opus 5 | $0.00059 | $0.01612 |
| Sonnet 5 | $0.00024 | $0.00645 |
| Haiku 4.5 | $0.00012 | $0.00322 |
Grade A, and why
pair 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 yesterday.
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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pair
Pair programming with a persistent Codex partner. Claude drives: edits files, runs tests. Codex navigates: reviews, critiques, suggests, in a read-only sandbox, with full memory of the session.
The wrapper
All Codex traffic goes through:
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-pair.mjs" <cmd> [flags]
Commands: start, send, list, end,
design-register, design-agree, design-amend,
review-start, review-complete, override-cap,
judge, snapshot. macOS and Linux only: the wrapper relies on
POSIX process groups to terminate the codex tree and
fails fast elsewhere. start and send read the prompt
from stdin; send requires
--kind design|review|freeform (freeform is uncounted).
Both print JSON with threadId, lastMessage, and
errors. State lives in ~/.claude/codex-pair/pairs.json
(schema v2; v1 files migrate automatically).
Always pass prompts via stdin from a temp file, never as
a shell-interpolated argument and never as a heredoc:
diffs contain quotes, backticks, $(...), and can even
contain your heredoc delimiter (this repo's own docs do),
which would truncate the prompt and feed the remainder to
the shell. Write the prompt with the Write tool, then:
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-pair.mjs" send \
--label <label> --kind <design|review|freeform> \
< "<prompt-file>"
Quote every interpolated path. Labels are validated by the wrapper (letters, digits, dot, dash, underscore only); pick labels that fit.
Run long partner turns in the background. send for
a review or design round takes minutes; run it as a
background task and keep working (write the next test,
prep the next change) until the completion notification,
then read the output file and relay the verdict. The
wrapper streams one [codex] ... line per partner
action to stderr, so tailing the task output file shows
live progress; read the tail, not the whole file, when
peeking mid-run. Never
have two in-flight sends for the same label: turns on
one thread are strictly serial. Short turns (status-like
questions) can stay foreground.
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.
- yesterday First seen · 339 lines · 118 tokens per session scan A c45fc15fee38
pair is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 118 tokens to every session and 3,224 once invoked, about $0.0006 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-31.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.