pair

pair is a command for coding agents from Achitokun14/claude-universal. It costs 17 tokens per session (395 once invoked), scanned A, original, MIT.

A command that asks two agents to examine the same question at the same time: one gathers facts from the codebase and the other designs possible approaches. Their findings are then combined.

In plain words
What is it for?
Use it to investigate an unfamiliar codebase, identify applicable patterns, compare approaches, and produce a recommended implementation plan.
Why use it?
It separates evidence gathering from solution design, giving you both the relevant constraints and several implementation options before work begins.

Command

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.

agentmods
npx agentmods add commands/achitokun14/claude-universal/pair
Clone the repo
git clone --depth 1 https://github.com/Achitokun14/claude-universal

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 pair

README.md
[![agentmods](https://agentmods.dev/badge/commands/achitokun14/claude-universal/pair.svg)](https://agentmods.dev/commands/achitokun14/claude-universal/pair)
Your own site
<a href="https://agentmods.dev/commands/achitokun14/claude-universal/pair"><img src="https://agentmods.dev/badge/commands/achitokun14/claude-universal/pair.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 395 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00395
Opus 5 $0.00009 $0.00198
Sonnet 5 $0.00003 $0.00079
Haiku 4.5 $0.00002 $0.00040

Measured 4d ago against content hash 789870fe0c13, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

user/commands/pair.md · 47 lines

What it actually says

Pair-programming pattern: run an Explore agent (gathers facts) and a Plan agent (designs approach) concurrently on the same question, then synthesize.

Steps:

  1. If $ARGUMENTS is empty, ask: "What's the question or task to pair on?".

  2. Dispatch in a SINGLE message with two Agent tool calls in parallel:

    • Explore agent (subagent_type: "Explore", thoroughness: "medium"):
      Explore the current codebase in service of this question: "$ARGUMENTS".
      Return: relevant files with line refs, existing patterns that apply, prior art,
      and concrete constraints (framework version, language, conventions). Facts only,
      no recommendations. Under 400 words.
      
    • Plan agent (subagent_type: "Plan"):
      Design an implementation approach for: "$ARGUMENTS". Assume the codebase will be
      explored separately — you focus on trade-offs, step ordering, and risk. Produce:
      2-3 viable approaches, 1 recommendation with rationale, explicit dependencies
      and sequencing. Under 400 words.
      
  3. When both return, synthesize into:

    # Pair result: $ARGUMENTS
    
    ## Explore (facts)
    <bullet distillation from Explore agent>
    
    ## Plan (approach)
    <bullet distillation from Plan agent>
    
    ## Synthesis
    **Recommended path:** <one sentence>
    **Key risks:** <bullets>
    **First step:** <one concrete action>
    
  4. Ask if the user wants to proceed with the recommended path, pick an alternative, or dig deeper.

Do not start implementing until the user chooses.

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. 4d ago First seen · 47 lines · 17 tokens per session scan A 789870fe0c13

Subscribe to this mod's changes

pair is a command published in the GitHub repository Achitokun14/claude-universal (2 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 395 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-31.