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 skills/supportersimulator/3-surgeons/consensusnpx skills add supportersimulator/3-surgeons --skill consensusgit clone --depth 1 https://github.com/supportersimulator/3-surgeonsWrote 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/supportersimulator/3-surgeons/consensus)<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/consensus"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/consensus.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.1 | $0.00016 | $0.01066 |
| Opus 5 | $0.00008 | $0.00533 |
| Sonnet 5 | $0.00003 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
consensus 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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consensus
When to Use
Consensus is the lightweight decision tool -- a quick confidence-weighted vote rather than a full cross-examination. Use it when:
- Validating a claim -- "Is this approach safe?" "Does this pattern follow best practices?"
- Checking assumptions -- before building on an assumption, verify it with both models
- Pre-commit verification -- "Will this change break backwards compatibility?"
- Resolving simple disagreements -- when you have two plausible options and need a tiebreaker
- Quick sanity checks -- "Is this the right data structure for this use case?"
Do NOT use for: complex architectural decisions (use cross-examination), health checks (use probe), or risk assessment (use sentinel).
How to Invoke
CLI
3s consensus "Redis LPUSH is O(1) for single elements"
MCP Tool
consensus(claim="Redis LPUSH is O(1) for single elements")
How It Works
Each surgeon receives the claim and responds with a JSON assessment:
{
"confidence": 0.85,
"assessment": "agree",
"reasoning": "Redis LPUSH is documented as O(1) per element..."
}
The system then calculates a weighted consensus score:
weighted_score = sum(confidence_i * assessment_value_i) / sum(confidence_i)
Where assessment values are: agree = +1.0, uncertain = 0.0, disagree = -1.0.
Interpreting the Weighted Score
| Score Range | Meaning | Action |
|---|---|---|
| +0.7 to +1.0 | Strong agreement | Proceed with confidence. Both surgeons agree the claim is valid. |
| +0.3 to +0.7 | Moderate agreement | Proceed but verify. One surgeon is less confident or uncertain. |
| -0.3 to +0.3 | Uncertain / Split | Do not proceed blindly. Consider escalating to full cross-examination. |
| -0.7 to -0.3 | Moderate disagreement | The claim is likely wrong or oversimplified. Investigate further. |
| -1.0 to -0.7 | Strong disagreement | The claim is rejected by both surgeons. Re-examine your assumption. |
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.
- 5d ago First seen · 113 lines · 16 tokens per session scan A 49267d5642eb
consensus is a skill published in the GitHub repository supportersimulator/3-surgeons (2 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,066 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-31.
Other skills, from other repositories
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
image-generation
Generate or edit images from text prompts. Use when the user asks to create, draw, design, or edit an image, illustration, photo, icon, poster, or any visual content.
deepcode-self-refer
Answers questions about Deep Code CLI itself — including features, configuration options, slash commands, Skills, MCP integration, permissions, notifications, session persistence, and troubleshooting. Use this when users ask how to configure or use Deep Code, how to set up an MCP server, configure notifications (such…
image-generator
Generate or edit images from text and local files, image URLs, or data URLs through image API. Use when the user asks to create an image, generate from one or more reference images, combine styles or elements across references, or edit a marked region while blending the result into the original scene.
weibo-poster
微博内容创作 - 140字优化、话题热搜、@提及策略、配图描述、发布时机.
xiaohongshu-writer
小红书笔记写作助手 - 标题优化、emoji策略、话题标签、封面文案、笔记结构.