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 commands/achitokun14/claude-universal/pairgit clone --depth 1 https://github.com/Achitokun14/claude-universalWrote 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/commands/achitokun14/claude-universal/pair)<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>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 | $0.00017 | $0.00395 |
| Opus 5 | $0.00009 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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.
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:
-
If
$ARGUMENTSis empty, ask: "What's the question or task to pair on?". -
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.
- Explore agent (
-
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> -
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.
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 First seen · 47 lines · 17 tokens per session scan A 789870fe0c13
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.
Other commands, from other repositories
dev-screenshot
Use the dev screenshot script to iterate on UI changes. This builds the Go server with dev tags, starts it on an isolated port, opens the browser, and captures a screenshot for visual verification.
publish
Publish a new release of Coral to PyPI. The user provides the version number as $ARGUMENTS (e.g. "2.2.0").
milestone-list
PitWay: List every milestone with a concise one-line status.
setup
Install the claude-pace statusline bundled with this plugin.
fix
Universal debugging and fix application with semantic code analysis.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.