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/hcaiano/skills/pairnpx skills add hcaiano/skills --skill pairgit clone --depth 1 https://github.com/hcaiano/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/hcaiano/skills/pair)<a href="https://agentmods.dev/skills/hcaiano/skills/pair"><img src="https://agentmods.dev/badge/skills/hcaiano/skills/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.00083 | $0.01659 |
| Opus 5 | $0.00042 | $0.00830 |
| Sonnet 5 | $0.00017 | $0.00332 |
| Haiku 4.5 | $0.00008 | $0.00166 |
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.
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 — any of them except the CLI you are
already running, because two panes of one CLI echo rather than review. 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.
The refusal is based only on the CLI kind. Two different harnesses may use the same underlying model or provider and still form a valid pair.
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 work cycle, read the measured pool state as
defined in references/models.md. Resume an existing
pair when its pool is available. When its pool is protected, state its use,
pace, and reset, then ask whether to spend it or end the session and choose
another partner. 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, ask the user in plain chat text — no structured-question tool needed — for three things, and start nothing until they answer. Read pool state first and do not recommend a protected or unavailable pool. The user may explicitly choose a protected pool after you state its use, pace, and reset:
- Partner: which of the five CLIs, other than yours.
- Model:
CLI default, or any model name they name. When choosing a model, effort, or pool, readreferences/models.md; it owns the risk, speed, context, catalog, and effort rubric. For a cursor partner runcursor-agent --list-models; for Grok rungrok models; for OpenCode runopencode models; for the others take the user's answer as given. - Effort: only for a partner that exposes it — Claude Code
(
--effort low|medium|high|xhigh|max), grok (--reasoning-effort), codex (model_reasoning_effort), or cursor (an[effort=…]suffix on the model name, so it needs a model too), or OpenCode (--varianton headlessopencode run; its Herdr TUI does not expose this flag).
What ships with it
21 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.
- agents/openai.yaml 256 B
- references/caller-pane-resolution.md 3.9 KB
- references/headless.md 13 KB
- references/herdr.md 12 KB
- references/models.md 13 KB
- references/workbench-tab.md 1.1 KB
- scripts/agent-process.mjs 712 B runs code
- scripts/agent-process.test.mjs 1.5 KB runs code
- scripts/caller-proof.mjs 12 KB runs code
- scripts/caller-proof.test.mjs 15 KB runs code
- scripts/fixtures/codex-stream.jsonl 230 B
- scripts/fixtures/cursor-stream.jsonl 404 B
- scripts/fixtures/grok-stream-cancelled.jsonl 129 B
- scripts/fixtures/grok-stream-complete.jsonl 258 B
- scripts/fixtures/grok-stream-incomplete.jsonl 76 B
- scripts/fixtures/opencode-stream.jsonl 517 B
- scripts/herdr-pair.mjs 75 KB runs code
- scripts/herdr-pair.test.mjs 80 KB runs code
- scripts/pair-headless.mjs 61 KB runs code
- scripts/pair-headless.test.mjs 75 KB runs code
- scripts/skill-contract.test.mjs 23 KB runs code
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 · 148 lines · 83 tokens per session scan A 42c7b5a02a22
pair is a skill published in the GitHub repository hcaiano/skills (3 stars, last pushed 13d ago), licensed MIT. It adds 83 tokens to every session and 1,659 once invoked, about $0.0004 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
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…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
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 disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
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-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…