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 flurdy/agent-skills --skill pair-programminggit clone --depth 1 https://github.com/flurdy/agent-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/flurdy/agent-skills/pair-programming)<a href="https://agentmods.dev/skills/flurdy/agent-skills/pair-programming"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/pair-programming/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/flurdy/agent-skills/pair-programming"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/pair-programming.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.00038 | $0.01414 |
| Opus 5.5 | $0.00015 | $0.00566 |
| Sonnet 5.5 | $0.00008 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
pair-programming 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 9d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair Programming
Work as a pair: discuss the change together; the agent writes the authorized code. The human does not have to type. Keep the connection between domain intent, code, and evidence visible without turning the conversation into a lesson or examination.
Activation and scope
Activate only for an explicit pairing request, such as “let's pair on this” or
“pair with me while you implement”, or invocation of this skill by name.
Claude Code: /pair-programming; Pi: /skill:pair-programming; other clients:
request the skill by name. Mentioning key pairs or asking an ordinary coding
question is not opting in. Loading this file for review is not activation.
Say briefly that you will write the code and pause between agreed steps to discuss results. Pairing changes interaction, not authority: activation alone grants no permission to edit, run commands, claim work, install anything, or publish changes. Discussion-only intent stays read-only until the user explicitly requests implementation; “sounds right” about an explanation is not that request.
Keep pairing active in the current session across skill handoffs until the user explicitly exits. It is an interaction layer, not an implementation specialist or an always-on gate. No extra orchestration, state files, or runtime dependencies are needed.
Agree on a small step
Use what the user has already told you: the desired outcome, relevant code and domain constraints, what must remain true, and any settled decisions. Read the relevant repository evidence rather than guessing. Ask only about missing context that materially changes the work; no fixed intake questionnaire.
Discuss meaningful alternatives in terms of behavior and trade-offs, and recommend an approach with reasons. Answer direct questions directly. Do not demand a prediction, quiz the user, or withhold an answer to test their understanding.
A step is one reviewable outcome plus proportionate verification, not one tool call and not an entire multi-part feature disguised as a step. Propose that boundary before starting. If the user already requested a concrete small implementation step, acknowledge its scope and proceed without asking for the same permission again. For a broad implementation request, agree on the first step before editing.
What ships with it
4 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.
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.
- 9d ago First seen · 122 lines · 38 tokens per session scan A 123a7fe44f5f
pair-programming is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,414 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-10-11.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…