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/backchainai/backchain-plugins/advisory-panelnpx skills add backchainai/backchain-plugins --skill advisory-panelgit clone --depth 1 https://github.com/backchainai/backchain-pluginsWrote 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/backchainai/backchain-plugins/advisory-panel)<a href="https://agentmods.dev/skills/backchainai/backchain-plugins/advisory-panel"><img src="https://agentmods.dev/badge/skills/backchainai/backchain-plugins/advisory-panel.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 | $0.00068 | $0.00952 |
| Opus 5 | $0.00034 | $0.00476 |
| Sonnet 5 | $0.00014 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
advisory-panel 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advisory Panel: Comprehensive Decision Analysis
You will analyze the following concept through four independent advisory perspectives using subagents for true isolation, then synthesize their insights into a unified recommendation.
Input
Decision/Idea to Analyze: $ARGUMENTS
Workflow Checklist
- Build context briefing from conversation (decision, background, constraints, stakeholders, prior analysis) — thorough enough that an advisor with no conversation history can produce a well-informed analysis
- Launch all 4 advisor subagents in parallel in a single message — each invokes its skill via
Skill("advisor-visionary", args: "<context briefing>")etc. — each runs in isolated context, producing structured output per its Output Format (200-400 words) - Collect all 4 analyses before proceeding
- Identify areas of agreement
- Identify areas of disagreement
- Extract critical callouts
- Generate risk-adjusted recommendation
Synthesis Detail
After all four subagents return their results, synthesize the findings:
Areas of Agreement
List insights where 3 or more advisors converge on the same conclusion, recommendation, or concern. For each area:
- State the common finding
- Note which advisors agree (by name)
- Include the strength of consensus (e.g., "All four advisors" vs "Three advisors")
Areas of Disagreement
List direct conflicts or tensions between advisors. For each disagreement:
- State the conflicting positions clearly
- Identify which advisors hold each position
- Explain the root cause of the disagreement (different priorities, risk models, timeframes, etc.)
Critical Callouts
One-line highlight from each advisor capturing their most important unique insight:
- Visionary Advisor: [single most transformative opportunity or constraint challenge]
- Skeptic Advisor: [single most critical risk or evidence gap]
- Operator Advisor: [single most critical execution concern or resource constraint]
- Ethicist Advisor: [single most important stakeholder impact or ethical consideration]
What ships with it
1 file 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 · 117 lines · 68 tokens per session scan A b4c25c97cdcd
advisory-panel is a skill published in the GitHub repository backchainai/backchain-plugins (4 stars, last pushed 28d ago), licensed Apache-2.0. It adds 68 tokens to every session and 952 once invoked, about $0.0003 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
kayba-stage-3-metrics
Define metrics from Kayba insights, implement them as Python measurement code, run against traces, and iterate until the metrics are clean and meaningful. Trigger when the user says "run stage 3", "define metrics", "build metrics", "compute baselines", or when invoked by the kayba-pipeline orchestrator. Requires…
kayba-stage-5-action-plan
Triage each insight into discard/code-fix/prompt-fix and produce a prioritized action plan with specific recommendations. Trigger when the user says "run stage 5", "make action plan", "triage skills", or when invoked by the kayba-pipeline orchestrator. Requires eval outputs from stages 1-4.
kayba-pipeline
End-to-end agent evaluation and improvement pipeline. Takes a traces folder and optional HITL flag, then orchestrates sub-agents through 7 stages — each stage is its own skill invoked by a dedicated sub-agent. Trigger when the user says "run the pipeline", "kayba pipeline", "evaluate and fix", "full eval", "analyze…
kayba-stage-2-domain-context
Gather domain context about the repository and agent — system prompt, tool definitions, domain docs, and behavior patterns from traces. Trigger when the user says "run stage 2", "gather context", "domain context", or when invoked by the kayba-pipeline orchestrator.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.
kayba-stage-1-api-analysis
Fetch pre-computed insights from the Kayba API and build a structured summary. Does NOT upload traces or trigger generation — analysis is assumed to already exist. Trigger when the user says "run stage 1", "get insights", "fetch skills", "kayba analyze", or when invoked by the kayba-pipeline orchestrator. Requires the…