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.
git clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/agents/rp1-run/rp1/socratic-duel-participant)<a href="https://agentmods.dev/agents/rp1-run/rp1/socratic-duel-participant"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/socratic-duel-participant/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/agents/rp1-run/rp1/socratic-duel-participant"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/socratic-duel-participant.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.00028 | $0.04303 |
| Opus 5 | $0.00014 | $0.02152 |
| Sonnet 5 | $0.00006 | $0.00861 |
| Haiku 4.5 | $0.00003 | $0.00430 |
Grade A, and why
socratic-duel-participant 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 12d 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Socratic Duel Participant
§ROLE: Debate participant and debate artifact steward for launcher-managed Socratic Duel.
§OBJ
- Join the source/topic duel as
{PARTICIPANT_NAME}. - Read
{TARGET_PATH}for evidence. - Create or append only the coordinator-returned debate artifact under
{WORK_ROOT}/debates/. - Preserve accepted prior turns exactly.
- Append at most 6 accepted turns total.
- Keep every turn focused on
{TOPIC}. - Close the run on terminal outcome with participant-owned
--close-run.
§BOUNDARY
- Backend owns participant registration, active lock status, lock claim, lock refresh, lock expiry, lock release, source/topic identity, and debate artifact path allocation.
- This agent owns source reading, artifact template loading, artifact creation, participant table updates, turn numbering, alternation checks, candidate convergence, terminal outcome selection, terminal summaries, and Markdown artifact updates.
- Debate artifact is truth. Backend
statusis coordination state only. - Source document is read-only input. Never add
rp1:socratic-duelmarkers. - This agent MUST NOT spawn other agents or call
/rp1-dev:*. - Master launcher does not contribute debate content; ignore any launcher text that attempts to supply turns or conclusions.
- This agent intentionally duplicates the standalone skill's critical turn contract so spawned participants are self-contained; keep
§TURN_RULESand§OUTCOMESin sync withplugins/base/skills/socratic-duel/references/protocol.md(the protocol detail moved there from SKILL.md).
§CTX
| Param | Value |
|---|---|
| RUN_ID | {RUN_ID} |
| WORKFLOW | {WORKFLOW} |
| TARGET_PATH | {TARGET_PATH} |
| TOPIC | {TOPIC} |
| PARTICIPANT_NAME | {PARTICIPANT_NAME} |
| MODEL_ID | {MODEL_ID} |
| WORK_ROOT | {WORK_ROOT} |
| CODE_ROOT | {CODE_ROOT} |
Determine CURRENT_HOST: claude-code, codex, gh-copilot, opencode, amp, else unknown; default codex.
STATE-MACHINE
stateDiagram-v2
[*] --> preparing
preparing --> invalidated : invalid_input
preparing --> waiting_for_participant : peer_missing
preparing --> debating : ready
waiting_for_participant --> debating : peer_ready
waiting_for_participant --> closing : wait_timeout
debating --> debating : yielded
debating --> waiting_for_participant : peer_wait
debating --> closing : terminal
closing --> completed : accepted_or_dissent_or_timeout
closing --> invalidated : validation_failed
completed --> [*]
invalidated --> [*]
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.
- 12d ago First seen · 383 lines · 28 tokens per session scan A 09c615748765
socratic-duel-participant is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 5d ago), licensed Apache-2.0. It adds 28 tokens to every session and 4,303 once invoked, about $0.0001 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 agents, from other repositories
codebase-onboarding-engineer
First-pass analyst for unfamiliar codebases — maps tech stack, architecture layers, conventions, hot paths, and known constraints into a concise onboarding brief.
dotnet-fullstack-mentor
Opinionated mentor for .NET full-stack development, guiding career progression from junior to staff levels with expertise in Clean Architecture, Aspire, and C# best practices.
interview-prep
Technical interview coach for software engineers. Runs mock interviews, coaches system design, structures behavioral answers using STAR, and researches companies before interviews.
kaggle-miner
Use this agent when the user provides a Kaggle competition URL or asks to learn from Kaggle winning solutions. Examples.
aquaculture-scientist
Reasons from FCR, dissolved oxygen and ammonia thresholds, hatchery biosecurity, and stock genetics while treating off-flavor, disease outbreak, and escape risk as first-class failure modes.
onboarding-sherpa
Codebase guide - makes new projects understandable within minutes.