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 skills add logicrw/agpair --skill hermesgit clone --depth 1 https://github.com/logicrw/agpairWrote 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/logicrw/agpair/hermes)<a href="https://agentmods.dev/skills/logicrw/agpair/hermes"><img src="https://agentmods.dev/badge/skills/logicrw/agpair/hermes/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.
<a href="https://agentmods.dev/skills/logicrw/agpair/hermes"><img src="https://agentmods.dev/badge/skills/logicrw/agpair/hermes.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00027 | $0.02014 |
| Opus 5.5 | $0.00011 | $0.00806 |
| Sonnet 5.5 | $0.00005 | $0.00403 |
| Haiku 4.5 | $0.00003 | $0.00201 |
Grade A, and why
agpair 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 2mo 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGPair for Hermes
Use AGPair as Hermes' durable external-agent control plane. Hermes remains the controller, verifier, and final decision maker.
Core rule: external-first, not external-always. For non-trivial coding, refactor, test-fix, research, review, or multi-file work, consider an AGPair lane before doing everything directly in Hermes. Skip AGPair when the task is tiny, highly sensitive, depends on hidden Hermes context, or requires local home-state inspection that should not be delegated.
Hermes is not an AGPair executor identity. Do not inherit Codex or Claude Code self-executor suppression. For Hermes controllers, all active external AGPair executors are valid:
grok-cliantigravity-clicodexclaude-code
Inspect the live policy before relying on exact ordering:
agpair policy list --controller hermes --json
If the policy and this skill disagree, the live AGPair policy is the execution
truth. Prefer explicit --executor when you want a specific lane.
When To Use
Use AGPair when an external worker can produce useful evidence:
- implementation candidates in isolated worktrees;
- independent code review or adversarial critique;
- repo scans, test-fix attempts, and repetitive verification;
- research or diagnosis with a bounded question;
- role-distinct fanout where each lane has a different scope, hypothesis, or review angle.
Use Hermes directly, or a Hermes native subagent, when the work is:
- a tiny local edit or one-command check;
- sensitive credential, auth, config, or memory inspection;
- dependent on current hidden conversation state;
- not safely isolatable for mutating external work;
- best handled as controller-side synthesis or final review.
AGPair-started workers do not share Hermes' hidden session state. Every AGPair brief must stand alone: include the goal, repo path, allowed scope, forbidden scope, constraints, required output, and validation/evidence requirements.
Routing Budget
Before dispatching, choose a routing budget:
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.
- 2mo ago First seen · 274 lines · 27 tokens per session scan A b0d6ce9ea506
agpair is a skill published in the GitHub repository logicrw/agpair (50 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 2,014 once invoked, about $0.0001 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-30.
agpair compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| agpairlogicrw/agpair | Skill | 50 | 4mo ago | MIT | A | 27 | Claude Code, Codex |
| feishuHmbown/CodeWhale | Skill | 41k | 2d ago | MIT | A | 33 | Claude Code, Codex |
| interviewHmbown/CodeWhale | Skill | 41k | 2d ago | MIT | A | 40 | Claude Code, Codex |
| refocusingmvschwarz/openrig | Skill | 8.8k | today | Apache-2.0 | A | 59 | Claude Code |
| recipe-create-meet-spacegoogleworkspace/cli | Skill | 32k | 7d ago | Apache-2.0 | A | 18 | Claude Code, Codex |
| printing-press-importmvanhorn/cli-printing-press | Skill | 4.9k | today | MIT | A | 104 | Claude Code |
| atmos-validationcloudposse/atmos | Skill | 1.4k | today | Apache-2.0 | A | 31 | Claude Code |