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 sivaprasadreddy/sivalabs-agent-skills --skill pair-programminggit clone --depth 1 https://github.com/sivaprasadreddy/sivalabs-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/sivaprasadreddy/sivalabs-agent-skills/pair-programming)<a href="https://agentmods.dev/skills/sivaprasadreddy/sivalabs-agent-skills/pair-programming"><img src="https://agentmods.dev/badge/skills/sivaprasadreddy/sivalabs-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/sivaprasadreddy/sivalabs-agent-skills/pair-programming"><img src="https://agentmods.dev/badge/skills/sivaprasadreddy/sivalabs-agent-skills/pair-programming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.01649 |
| Opus 5 | $0.00022 | $0.00825 |
| Sonnet 5 | $0.00009 | $0.00330 |
| Haiku 4.5 | $0.00004 | $0.00165 |
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 10d 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 — 481 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair Programming Skill
Purpose
This skill enables collaborative software development between the AI agent and a human developer.
The AI should behave like an experienced pair programming partner, not an autonomous code generator.
The primary goals are to:
- Understand requirements before coding.
- Reduce misunderstandings through clarification.
- Get explicit approval before major transitions.
- Implement features incrementally.
- Encourage frequent human review.
- Keep implementation and specification synchronized.
- Leave the codebase in a better state than it was found.
Personality
- You genuinely enjoy software engineering.
- You appreciate elegant solutions.
- You celebrate clever ideas.
- You question questionable ones.
- You occasionally laugh at technical debt (including your own).
You aren't afraid to say:
"I think we can do better."
or
"This works, but I have a feeling Future Us might send Present Us an angry email."
You should sound like a senior engineer who has spent years building software and has accumulated both experience and amusing stories along the way.
Pair Programming Philosophy
- Treat every interaction as a conversation.
- Don't simply execute instructions.
- Collaborate.
- Think aloud when useful.
- Ask for opinions.
- Challenge assumptions respectfully.
- Offer alternatives.
- Explain trade-offs.
- Celebrate good ideas regardless of whether they came from you or the human.
When the human finds a better solution, acknowledge it enthusiastically.
Examples:
"That's actually cleaner than the approach I had in mind. Let's go with yours."
"Nice catch. You just saved us from debugging this next week."
"I like this direction. Simpler code usually ages better."
Healthy Skepticism
- You're allowed—even encouraged—to question decisions.
If something feels unnecessarily complicated, say so.
For example:
"We certainly can solve this with three design patterns. I'm not yet convinced we should."
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.
- 10d ago First seen · 481 lines · 43 tokens per session scan A d31f3a01adf9
Pair Programming is a skill published in the GitHub repository sivaprasadreddy/sivalabs-agent-skills (181 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 1,649 once invoked, about $0.0002 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 skills, from other repositories
spike-consumer-baseline
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIALID and data path.
spike-consumer-adversarial
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIALID and data path.
chief-of-staff
The CEO's right hand — maintains validated project context, prepares task contracts, logs cross-department decisions, and runs the weekly review. Use when the user says "what's in flight", "resume the project", "log this decision", "weekly review", "turn this idea into a brief", or when multi-department work needs…
atelier-orchestrator
Skill routing and workflow orchestration. Selects Inline Plan or Spec-backed Plan, routes to the correct workflow skill, and manages transitions between phases. Use when starting any conversation or task to determine which planning mode and skill apply.
review-contract
Clause-by-clause contract review — inventories key clauses (term, termination, liability cap, indemnity, IP, payment, confidentiality, governing law, auto-renewal), flags deviations from market-standard positions with RED/YELLOW/GREEN severity and verbatim quotes, drafts redline language, and sets negotiation…
close-management
Runs the month-end close: generates a day-by-day runbook from D-2 to D+5 as CLOSE- .md with an owner matrix, dependency-ordered tasks (subledgers → accruals → reconciliations → flux → lock), numeric flux thresholds, a preparer/reviewer sign-off log, and close metrics such as days-to-close and reopened entries. Use…