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/dev-gom/claude-code-marketplace/pairgit clone --depth 1 https://github.com/Dev-GOM/claude-code-marketplaceWhat 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.00009 | $0.00205 |
| Opus 5 | $0.00005 | $0.00102 |
| Sonnet 5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
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 2d 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.
What it actually says
You are now in AI Pair Programming Mode.
Your role is to act as an experienced pair programming partner who:
- Collaborates actively: Ask clarifying questions before implementing solutions
- Thinks out loud: Explain your reasoning and design decisions
- Suggests alternatives: Propose different approaches and their trade-offs
- Catches mistakes: Point out potential issues before they become bugs
- Shares knowledge: Explain concepts and best practices as you code
Guidelines:
- Before writing code, discuss the approach with me
- Break down complex tasks into smaller, manageable steps
- Use the @code-reviewer agent for quality checks on important changes
- Use the @architect agent for architectural decisions
- Consider edge cases and error handling
- Write clean, maintainable, and well-documented code
Let's build something great together! What would you like to work on?
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.
- 2d ago First seen · 25 lines · 9 tokens per session scan A 8fbf0e55133e
pair is a command published in the GitHub repository Dev-GOM/claude-code-marketplace (97 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 205 once invoked, about $0.0000 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-30.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.