A way for two different coding agents to work together on one task, with one leading and the other reviewing or helping. It can keep the partnership active across separate work sessions.

Use it for paired coding, review, problem solving, and workflows that send messages between agents. It supports Claude, Codex, Cursor, Grok, and OpenCode, with visible or background sessions.

It gives you a second agent's input instead of relying on one agent's reasoning. It also supports continuing the same partnership after a session loses its context.

pair — Skill for Codex by hcaiano/skills

Install

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.

Any agent

npx skills add hcaiano/skills --skill pair

Clone the repo

git clone --depth 1 https://github.com/hcaiano/skills

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hcaiano/skills/pair/github.svg)](https://agentmods.dev/skills/hcaiano/skills/pair)

Your own site

<a href="https://agentmods.dev/skills/hcaiano/skills/pair"><img src="https://agentmods.dev/badge/skills/hcaiano/skills/pair/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hcaiano/skills/pair"><img src="https://agentmods.dev/badge/skills/hcaiano/skills/pair.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,599 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.01599
Opus 5.5	$0.00018	$0.00640
Sonnet 5.5	$0.00009	$0.00320
Haiku 4.5	$0.00004	$0.00160

Measured 20d ago against content hash 82227c6115b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 20d ago.

The scan reads SKILL.md. This mod also ships 14 executable files (scripts/agent-process.mjs, scripts/agent-process.test.mjs, scripts/caller-proof.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

deprecated/pair/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pair

Pair two agents on one task: you are the lead, and the partner is one of claude, codex, cursor, grok, or opencode. The transports require a different CLI, except headless Codex can use a different account home selected with --identity <name>. The helper proves home separation; separate accounts do not themselves guarantee independent reasoning. Two different harnesses may use the same underlying model or provider and still form a valid pair. Keep the pair and its sid alive across tasks, accepted work cycles, and context compaction, naming its sid in every command — one lead can run several pairs at once. Keep protocol headers and identifiers literal.

Two backends carry the same protocol. Inside Herdr the partner is a visible pane the user can read and interject in; outside it the partner is a persistent headless session of the partner CLI.

Choose the pair

Look for an existing pair before proposing one: a session recorded for this Herdr tab, or a headless one in this repository (the backend reference names the exact command). Before a new pair or work cycle, run the pool check and follow its rule for each state. Resume an existing pair the check allows; for a live pair the check's fallback is ending it, which only the user can choose. When its partner, model, or effort differs from what the user just asked for, say so and keep going — respawning discards the pair's whole history, and a model is changed by ending the pair, not by restarting its pane.

With no pair to resume, run the catalog check before choosing the partner. Take every choice the user or an orchestrate unit has already made — partner, model, effort, identity, role — as final and do not ask for it again. Fill unspecified choices from the roster and the live pool check: the Peer seat for an equal collaborator, the Executor seat for delegated implementation. Use peer when the task leaves the role open. The seat supplies partner family, model, and effort; for Codex, choose the available identity with the lower pace (default is ~/.codex, a named home is ~/.codex-profiles/<name>). Ask the user in plain chat text only when no eligible route remains or their preference is ambiguous.

Read the full file on GitHub · 148 lines

Files

What ships with it

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

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.

20d ago Changed · -7 lines 82227c6115b2
1mo ago Changed · +7 lines · -39 tokens per session 1905b4cdaf18
1mo ago First seen · 148 lines · 83 tokens per session scan A 42c7b5a02a22

Subscribe to this mod's changes

pair is a skill published in the GitHub repository hcaiano/skills (3 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 1,599 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-08-31.

Building agents Claude Code agent-skills ai-agents claude codex skills

claude-md-improver

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…

anthropics/claude-plugins-official · 82 tokens

agent-platform-model-registry

Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.

google/skills · 60 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…

google/skills · 171 tokens

gke-reliability

Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…

google/skills · 85 tokens

google-cloud-solution-agentic-analytics-spark-knowledge-catalog

Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…

google/skills · 132 tokens

glance-canonical-layouts

Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).

android/skills · 56 tokens