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 ayushcodes10/echo-mem --skill pair-programminggit clone --depth 1 https://github.com/ayushcodes10/echo-memWrote 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/ayushcodes10/echo-mem/pair-programming)<a href="https://agentmods.dev/skills/ayushcodes10/echo-mem/pair-programming"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/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/ayushcodes10/echo-mem/pair-programming"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/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.00061 | $0.06281 |
| Opus 5.5 | $0.00024 | $0.02512 |
| Sonnet 5.5 | $0.00012 | $0.01256 |
| Haiku 4.5 | $0.00006 | $0.00628 |
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 1mo 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.
This is a copy
100% identical to Pair Programming — 124 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair Programming
Collaborative AI pair programming with intelligent role management, real-time quality monitoring, and comprehensive development workflows.
What This Skill Does
This skill provides professional pair programming capabilities with AI assistance, supporting multiple collaboration modes, continuous verification, and integrated testing. It manages driver/navigator roles, performs real-time code review, tracks quality metrics, and ensures high standards through truth-score verification.
Key Capabilities:
- Multiple Modes: Driver, Navigator, Switch, TDD, Review, Mentor, Debug
- Real-Time Verification: Automatic quality scoring with rollback on failures
- Role Management: Seamless switching between driver/navigator roles
- Testing Integration: Auto-generate tests, track coverage, continuous testing
- Code Review: Security scanning, performance analysis, best practice enforcement
- Session Persistence: Auto-save, recovery, export, and sharing
Prerequisites
Required:
- Codex Flow CLI installed (
npm install -g Codex-flow@alpha) - Git repository (optional but recommended)
Recommended:
- Testing framework (Jest, pytest, etc.)
- Linter configured (ESLint, pylint, etc.)
- Code formatter (Prettier, Black, etc.)
Quick Start
Basic Session
# Start simple pair programming
Codex-flow pair --start
TDD Session
# Test-driven development
Codex-flow pair --start \
--mode tdd \
--test-first \
--coverage 90
Complete Guide
Session Control Commands
Starting Sessions
# Basic start
Codex-flow pair --start
# Expert refactoring session
Codex-flow pair --start \
--agent senior-dev \
--focus refactor \
--verify \
--threshold 0.98
# Debugging session
Codex-flow pair --start \
--agent debugger-expert \
--focus debug \
--review
# Learning session
Codex-flow pair --start \
--mode mentor \
--pace slow \
--examples
Session Management
# Check status
Codex-flow pair --status
# View history
Codex-flow pair --history
# Pause session
/pause [--reason <reason>]
# Resume session
/resume
# End session
Codex-flow pair --end [--save] [--report]
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.
- 1mo ago Changed 9e339d7c804e
- 1mo ago First seen · 1,203 lines · 61 tokens per session scan A 32ef344d86f6
Pair Programming is a skill published in the GitHub repository ayushcodes10/echo-mem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 6,281 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to Pair Programming, differing in 124 lines, and is treated as a copy.
Other skills, from other repositories
pre-pr
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.
tdd-with-memory
A test-first implementation workflow that recalls past decisions, conventions, and lessons before coding. TDD, or test-driven development, means writing a failing test first, then implementing the code and finally cleaning it up.
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
risk-based-code-review
Use when reviewing or verifying software changes before completion, release, merge, deployment, or acceptance, especially when the appropriate test depth is unclear or security, data, migrations, external interfaces, infrastructure, or user-visible behavior may be affected.
Pair Programming
AI-assisted pair programming with multiple modes (driver$navigator$switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
ast-pe
An engineering delivery role for turning an approved design into working, tested, reviewable, and reversible software across modules. It covers implementation, integration, debugging, and delivery checks.