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 sdewell/code-quorum --skill q-validategit clone --depth 1 https://github.com/sdewell/code-quorumWrote 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/sdewell/code-quorum/q-validate)<a href="https://agentmods.dev/skills/sdewell/code-quorum/q-validate"><img src="https://agentmods.dev/badge/skills/sdewell/code-quorum/q-validate/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/sdewell/code-quorum/q-validate"><img src="https://agentmods.dev/badge/skills/sdewell/code-quorum/q-validate.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.00054 | $0.01676 |
| Opus 5.5 | $0.00022 | $0.00670 |
| Sonnet 5.5 | $0.00011 | $0.00335 |
| Haiku 4.5 | $0.00005 | $0.00168 |
Grade A, and why
q-validate 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Q-Validate — multi-round plan review
Completion gate
For every council start, q_await is the blocking completion notification. After completing the host's independent work, call it in the same turn as the start. Do not end the turn, tell the user you will check later, or leave a live job_id pending. If the council is still running, remain in the blocking call until it returns a result or error.
Arguments
$ARGUMENTS is the path to the plan file, optionally with --verbose to lift
the terse output caps and/or --gemini-model <id> to run the gemini seat on a
specific agy model. Strip --verbose and --gemini-model <id> from the path
before passing plan_path. If the remaining path is empty, ask the user which
plan file to review.
Host routing
Claude Code uses the mcp__plugin_code-quorum_quorum__* tools and passes
host: "claude". Codex uses the mcp__quorum_codex__* tools and passes
host: "codex". The workflows are otherwise identical.
If either required MCP tool is absent from the current task's tool registry, stop and report that the plugin MCP server did not load. Do not substitute the synchronous CLI, direct Python imports, or another runtime path: only the registered start/await pair enforces the structural anti-bias gate.
Every MCP council start requires an explicit absolute cwd. Never omit it: the
MCP server's own working directory is its installation or runtime location, not
the project selected by the user.
Step 1 — Start the agents (non-blocking)
Call mcp__plugin_code-quorum_quorum__q_validate_start (Claude Code) or
mcp__quorum_codex__q_validate_start (Codex) with:
plan_path: a bare file path only (absolute, or relative tocwd) that resolves insidecwd; paths outside the working directory are rejected before reading.q_validate_startopen()s this path directly, so it CANNOT carry an appended context/boundaries block — passing<path>+ prose errors withFile name too long. If$ARGUMENTSincludes reviewer context beyond the path, do NOT forward it here; instead put that context, boundaries, or specific questions inside the plan file (e.g. an## Open questions for reviewsection) — the agents read the file.cwd: the absolute path of the project working directoryhost: the current host selected aboveextended:falseby default (2-round review). Settruefor a 4-round deliberation with a stance rotation at round 3 — use only when the plan is contentious or high-stakes.mode:"revise"(default) — agents soften or strengthen positions in light of peers. Use"critique"when you want them to attack each other's points.agents: optional; omit it for every external seat in the current host profile (a seat the user has marked disabled inquorum setup-modelsis skipped from that default roster). Passingagentsexplicitly overrides the skip and runs a disabled seat anyway — a deliberate ask always runs.verbose:falseby default. The council writes terse output — no prose padding,path:linecitations instead of pasted code, and later rounds omit restating what is unchanged. Settrueonly if the user gave--verbose; it produces a much larger matrix.gemini_model: omit by default. Pass an agy model id (exactly as printed byagy models) when the user gave--gemini-model <id>or asked for a specific model in the gemini seat — e.g.claude-opus-5-5-highto have that seat answer with Claude on the same AI Pro plan.
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.
- 8d ago Changed 80380420458c
- 2mo ago First seen · 96 lines · 54 tokens per session scan A 8b2da4c5a742
q-validate is a skill published in the GitHub repository sdewell/code-quorum (1 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,676 once invoked, about $0.0002 per session on Opus 5.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
incident-review
Summarize an incident with timeline, likely cause, impact, and follow-up actions.
vnpy-export
Export a Vibe-Trading backtest strategy to a runnable vnpy CtaTemplate Python class — supports A-share equities, futures, and crypto via BarGenerator + ArrayManager.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Workflow guidance for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files under python/.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
splitting-oversized-modules
Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior. Use on a request to split / break up / decompose a god module or move functions out of one, once a human has agreed to…