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/fomo-driven-development/strategic-claude-base/pair-session.templategit clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWrote 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/fomo-driven-development/strategic-claude-base/pair-session.template)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/pair-session.template"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/pair-session.template.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.00000 | $0.02148 |
| Opus 5 | $0.00000 | $0.01074 |
| Sonnet 5 | $0.00000 | $0.00430 |
| Haiku 4.5 | $0.00000 | $0.00215 |
Grade A, and why
pair-session.template 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair Programming Session: [Session Focus/Feature Name]
Session ID: PAIR_[NNNN][DD-MM-YYYY][session-focus] Date: [YYYY-MM-DD] Duration: [HH:MM] - [HH:MM] Repository: [Repository name] Branch: [Current branch name]
Session Overview
Goals and Context
Primary Objective: [What we're trying to accomplish] Success Criteria:
- [Specific deliverable 1]
- [Specific deliverable 2]
- [Quality gate or validation requirement]
Background Context: [Why this work is needed, related tickets, prior decisions]
Communication Protocol
Style: [Strong|Traditional|Ping-Pong|Leap-Frog|Rubber-Duck|Mob] Role Swap Frequency: [Every X minutes or at natural breakpoints] Escalation Protocol: [How to handle disagreements or blockers]
Participants
- Driver (Initial): [Name/Agent] - Tactical implementation and coding
- Navigator (Initial): [Name/Agent] - Strategic guidance and quality oversight
Session Log
Role Swap History
| Time | Event | Driver | Navigator | Reason | Knowledge Transfer |
|---|---|---|---|---|---|
| [HH:MM] | Session Start | [Initial Driver] | [Initial Navigator] | Session initiation | [Context shared] |
| [HH:MM] | Role Swap | [New Driver] | [New Navigator] | [Reason for swap] | [Key points transferred] |
Code Reference Log
| Time | File:Line | Discussion Point | Decision | Outcome |
|---|---|---|---|---|
| [HH:MM] | [file:line] |
[What was discussed] | [Decision made] | [Implementation result] |
Communication Events
[HH:MM] - Navigation Guidance
Navigator: [Strategic guidance provided] Driver: [Response or clarification] Outcome: [How this influenced implementation]
[HH:MM] - Problem Solving
Issue: [Problem encountered]
Discussion: [How it was analyzed]
Solution: [Approach decided]
Implementation: [file:line] - [Where solution was applied]
[HH:MM] - Pattern Recognition
Pattern Identified: [Design pattern or architectural approach]
Reference: [example-file:line] - [Where pattern is demonstrated]
Application: [How pattern was applied to current work]
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 · 254 lines · 0 tokens per session scan A ac865481ac9b
pair-session.template is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,148 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.