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 timharris707/skills --skill advisory-boardgit clone --depth 1 https://github.com/timharris707/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/timharris707/skills/advisory-board)<a href="https://agentmods.dev/skills/timharris707/skills/advisory-board"><img src="https://agentmods.dev/badge/skills/timharris707/skills/advisory-board/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/timharris707/skills/advisory-board"><img src="https://agentmods.dev/badge/skills/timharris707/skills/advisory-board.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.00052 | $0.07379 |
| Opus 5.5 | $0.00021 | $0.02952 |
| Sonnet 5.5 | $0.00010 | $0.01476 |
| Haiku 4.5 | $0.00005 | $0.00738 |
Grade A, and why
advisory-board 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 28d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advisory Board
Read the Codex desktop binding when this workflow needs harness mechanics, model routing, or recovery.
Bring an idea, problem, plan, or architecture to a board of frontier models sitting in different roles. The board runs in one of three modes, the interaction topology chosen with the user at intake (references/modes.md). Formal Board Review is the default and the protocol this document defines: an independent first round, then rebuttal, then a structured verdict. Roundtable is collaborative, on a shared transcript, with an optional moderator. Competitive runs pitch, then critique, then a blind vote. Whatever the mode, you leave with the strongest conclusion the board can reach together and a clean takeaway, not disconnected opinions.
Must Not
Hard rules, collected here so they are never missed (each is elaborated in context below). Violating one invalidates the run.
- Never write files or make edits unless the user explicitly asked for edits: the board is read-only by default.
- Never write artifacts into a tracked git tree without naming the location first; default to the persistent runs root (
~/.advisory-board/runs/<slug>-<date>/), or a throwaway/tmp/advisory-board-*folder with--ephemeral. - Never substitute a model silently: if a requested model is unavailable, use the nearest same-provider frontier model and say so.
- Never skip the data-handling disclosure for non-public material, not even when the user says "use defaults." Disclose what leaves the machine and to whom, and get a go-ahead, before any external seat runs (
references/data-handling.md). - Never present a degraded or dropped seat as a full board: label it on the seat card and in
verdict.json(dropped: true) on a Formal Board Review run; Roundtable and Competitive, which emit noverdict.json, record it inrun-metadata.mdand name it insynthesis.md/results.md(references/modes.md). A board needs at least two seats that actually ran. - Never print or store secrets in prompts, packets, artifacts, logs, or metadata: no keys, tokens, cookies, or private environment values.
- Never launch a run the user hasn't confirmed. The guided intake (
references/intake-interview.md) is mandatory: mode, seats, lenses, effort, rounds, and output are the user's choices, made on the record. An already explicit approval of a complete plan satisfies its confirmation; reuse it. "Use defaults" still needs a concrete plan when seats, cost, or data scope have not yet been established.
What ships with it
60 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.
- agents/openai.yaml 236 B
- CHANGELOG.md 133 KB
- README.md 7.8 KB
- references/board-composition.md 5.4 KB
- references/changes-schema.md 13 KB
- references/data-handling.md 7.4 KB
- references/epistemics.md 7.2 KB
- references/execution-harness.md 5.8 KB
- references/handoff-template.html 38 KB
- references/implementation-sequence-template.html 20 KB
- references/intake-interview.md 5.8 KB
- references/lens-presets.md 6.1 KB
- references/modes.md 11 KB
- references/output-formats.md 6.7 KB
- references/plan-fonts.css 170 KB
- references/plan-template.html 21 KB
- references/preflight.md 7.3 KB
- references/prompt-templates.md 18 KB
- references/quick-verdict-template.html 16 KB
- references/run-metadata-template.md 2.3 KB
- references/verdict-schema.md 22 KB
- scripts/_conductor/__init__.py 268 B runs code
- scripts/_conductor/artifacts.py 38 KB runs code
- scripts/_conductor/ask.py 27 KB runs code
- scripts/_conductor/cli.py 110 KB runs code
- scripts/_conductor/config.py 52 KB runs code
- scripts/_conductor/constants.py 22 KB runs code
- scripts/_conductor/convergence.py 21 KB runs code
- scripts/_conductor/delta.py 6.9 KB runs code
- scripts/_conductor/digest.py 12 KB runs code
- scripts/_conductor/doctor.py 12 KB runs code
- scripts/_conductor/echo_score.py 15 KB runs code
- scripts/_conductor/egress.py 23 KB runs code
- scripts/_conductor/endorsement.py 29 KB runs code
- scripts/_conductor/grounding.py 33 KB runs code
- scripts/_conductor/history.py 8.8 KB runs code
- scripts/_conductor/preflight.py 9.5 KB runs code
- scripts/_conductor/prompts.py 44 KB runs code
- scripts/_conductor/recipe.py 20 KB runs code
- scripts/_conductor/redline.py 9.1 KB runs code
- scripts/_conductor/registry.py 34 KB runs code
- scripts/_conductor/revise.py 18 KB runs code
- scripts/_conductor/revision.py 53 KB runs code
- scripts/_conductor/rounds.py 26 KB runs code
- scripts/_conductor/rubric.py 69 KB runs code
- scripts/_conductor/scorecard.py 12 KB runs code
- scripts/_conductor/spawn.py 11 KB runs code
- scripts/_conductor/status.py 24 KB runs code
- scripts/_conductor/synthesizer.py 37 KB runs code
- scripts/_conductor/toolchain.py 10 KB runs code
- scripts/_embed_fonts.py 2.3 KB runs code
- scripts/_md.py 11 KB runs code
- scripts/_render_engine.py 6.5 KB runs code
- scripts/_severity_filter.py 4.2 KB runs code
- scripts/_verdict_labels.py 9.2 KB runs code
- scripts/board_changes.py 20 KB runs code
- scripts/board_rubric.py 17 KB runs code
- scripts/board_scorecard.py 27 KB runs code
- scripts/board_verdict.py 42 KB runs code
- scripts/format_output.py 9.3 KB runs code
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.
- 28d ago First seen · 231 lines · 52 tokens per session scan A 9bf73da81eae
advisory-board is a skill published in the GitHub repository timharris707/skills (41 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 7,379 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-09-21.
Other skills, from other repositories
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
cyxj-blog-pub
A publishing workflow for adding a finished article to an Astro blog, a website built with the Astro framework.
cyxj-transcript
A workflow that turns a video or audio transcript into a structured article draft in Obsidian Markdown.
document
Generate minimal documentation through parallel agents.
plan
Use when a CCF-initialized project is in plan mode, after the user types /plan, or when they ask to plan a feature or change (lên kế hoạch, plan a change). Creates an implementation plan of vertical slices with declared dependencies, which /ccf:cook runs in parallel waves, grounded in best practices, with an…
cyxj-jingxuan
A writing assistant for applying to have a finished video selected for 抖音精选, a curated feature on the Douyin video platform. It reads the video's actual subtitles or transcript and writes a 150–250 character Chinese application in four sections.