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 marcusgoll/Spec-Flow --skill multi-agent-votinggit clone --depth 1 https://github.com/marcusgoll/Spec-FlowWrote 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/marcusgoll/spec-flow/multi-agent-voting)<a href="https://agentmods.dev/skills/marcusgoll/spec-flow/multi-agent-voting"><img src="https://agentmods.dev/badge/skills/marcusgoll/spec-flow/multi-agent-voting.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.00000 | $0.01589 |
| Opus 5 | $0.00000 | $0.00794 |
| Sonnet 5 | $0.00000 | $0.00318 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
multi-agent-voting 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 3d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Voting Skill
Execute multi-agent voting for critical decisions using MAKER-style first-to-ahead-by-k error correction.
When to Use
Use this skill when:
- Making critical decisions that benefit from consensus (code review, breaking changes, spec validation)
- Voting is enabled in
.spec-flow/config/voting.yamlfor the operation type - High-stakes decisions where single-agent errors are unacceptable
Theoretical Foundation
Based on MAKER paper (arXiv:2511.09030):
- First-to-ahead-by-k voting: Candidate must be k votes ahead to win
- Formula:
p_correct = p^k / (p^k + (1-p)^k) - Scaling: Cost grows log-linearly O(s ln s) with decomposition
With k=2 and individual agent accuracy of 70%:
- Single agent: 70% accuracy
- 3 agents with k=2: ~84% accuracy
- 5 agents with k=3: ~91% accuracy
Prerequisites
Workflow
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 234 lines · 0 tokens per session scan A 104018179dce
multi-agent-voting is a skill published in the GitHub repository marcusgoll/Spec-Flow (92 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,589 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-09-03.
Other skills, from other repositories
improve-codebase-architecture
Avaliar a arquitetura de um codigo existente, encontrar friccoes comprovaveis, gerar obrigatoriamente um relatorio HTML e propor refatoracoes incrementais com impacto tecnico e de produto. Usar quando o usuario pedir melhoria arquitetural, crescimento sustentavel, reducao de acoplamento, modulos mais testaveis ou um…
code-review
Run a comprehensive code review.
skill-scope-control
Analisa se alterações, diffs e PRs continuam alinhados ao objetivo declarado, identificando escopo extra e propondo manter, separar ou justificar.
refactoring-assistant
A guide for deciding how to improve existing code, including when to refactor it gradually or replace it with a rewrite. Refactoring changes code structure without changing what it is meant to do.
code-review-assistant
A checklist for reviewing code changes and pull requests. A pull request is a proposed change that teammates inspect before adding it to the shared codebase.
code-simplifier
Use when user asks to simplify, clean up, or refactor recently modified code for readability, consistency, or maintainability without changing behavior, especially after implementation and before broader review.