multi-expert-analyzer

multi-expert-analyzer is a skill for Claude Code, Codex from digoal/blog. It costs 230 tokens per session (6,231 once invoked), scanned A, original, GPL-2.0.

A method for examining difficult questions from several expert perspectives, with evidence checks and a separate challenge of the conclusions.

In plain words
What is it for?
Deep multi-perspective analysis, first-principles reasoning, fact-checking, and testing whether conclusions can be challenged.
Why use it?
It is intended for disputed, cross-field, or evidence-heavy questions where a single straightforward answer may miss important issues.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

About the project

digoal/blog is a large collection of Chinese-language articles, courses, videos, and practical learning materials about databases, especially PostgreSQL and related systems, along with topics such as AI, open source, business, and finance. It is for database administrators, developers, architects, and others learning database technologies and their applications.

digoal/blog · 8,570 stars · on GitHub

Install

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.

agentmods
npx agentmods add skills/digoal/blog/multi-expert-analyzer
Any agent
npx skills add digoal/blog --skill multi-expert-analyzer
Clone the repo
git clone --depth 1 https://github.com/digoal/blog

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for multi-expert-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/digoal/blog/multi-expert-analyzer.svg)](https://agentmods.dev/skills/digoal/blog/multi-expert-analyzer)
Your own site
<a href="https://agentmods.dev/skills/digoal/blog/multi-expert-analyzer"><img src="https://agentmods.dev/badge/skills/digoal/blog/multi-expert-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 230 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,231 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00230 $0.06231
Opus 5 $0.00115 $0.03116
Sonnet 5 $0.00046 $0.01246
Haiku 4.5 $0.00023 $0.00623

Measured 6d ago against content hash b7fe9d8ba9f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

multi-expert-analyzer 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 6d 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.

skills/multi-expert-analyzer/SKILL.md · 383 lines

The source is not reproduced here

Licensed GPL-2.0

The repository is licensed GPL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 6d ago First seen · 383 lines · 230 tokens per session scan A b7fe9d8ba9f6

Subscribe to this mod's changes

multi-expert-analyzer is a skill published in the GitHub repository digoal/blog (8,570 stars, last pushed today), licensed GPL-2.0. It adds 230 tokens to every session and 6,231 once invoked, about $0.0011 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-30.

Related

Other skills, from other repositories

safe-sql-execution

Use whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix and never says "security," "injection," or "SafeSqlFragment." This covers: writing or editing any pg-meta function, query builder, or endpoint…

supabase/supabase · 221 tokens

ask-the-docs

Answer questions about the Supabase docs app (apps/docs) using documented architecture, build pipeline, and review-pattern notes, and apply feature-design principles (codebase reuse, coding minimalism) when proposing or critiquing changes. Use when the user asks "how does X work in the docs app?", "where does Y…

supabase/supabase · 129 tokens

clickhouse-logs-queries

Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint). Use this whenever a task involves Logs Explorer SQL, the logattributes map, querying a log source (edgelogs, postgreslogs, authlogs, etc.), translating an old BigQuery cross join…

supabase/supabase · 152 tokens

studio-testing

Testing strategy for Supabase Studio. Use when writing tests, deciding whether a change needs tests and which type, extracting logic from components into testable utility functions, or reviewing test coverage. Covers unit tests, component tests, and E2E test selection criteria.

supabase/supabase · 55 tokens

studio-queries

React Query conventions for data fetching in Supabase Studio. Use when writing or reviewing query hooks, mutation hooks, or query keys in apps/studio/data/ — including adding the first fetch or mutation for a new API endpoint or resource. Covers queryOptions pattern, keys.ts structure, mutation hook template, and…

supabase/supabase · 68 tokens

explorer

Build and modify Studio Explorer surfaces, including notebooks, chats, SQL snippets, query cells, and their shared toolbar patterns.

supabase/supabase · 27 tokens