Claude Council

Claude Code plugin that asks several AI coding agents the same question and shows their answers side by side. Gemini, OpenAI, Grok, Perplexity, Kimi and any model OpenRouter routes to over API; codex, antigravity, grok, kimi and cursor CLIs on subscription auth; ollama locally. Codex specialists…

Agent Skills Shell Listed MIT

Is Claude Council safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.4 / 10
Provenance None
Signed commits 8%
Last push today
Compare Claude Council
Suggest a correction

In detail: Claude Council scores 56.4/100 (Grade C), ranked #168 of 396 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.4/10; 8% of recent commits are signed; last pushed 2026-11-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Council could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Claude Council and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/hex/claude-council, MIT, last pushed 2026-11-17. 8% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.4/10 (scanned Nov 15, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 4
    SAST 0
    Security-Policy 9
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 10
  3. Published packages None

    No registry package. Claude Council is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 4.1/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Claude Council’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Claude Council compares in Agent Skills

  1. #166 Plinth 56.5 +0.1
  2. #167 Fireworks Tech Graph 56.5 +0.1
  3. #168 Claude Council 56.4 this agent
  4. #169 Claude Code Hooks 56.4 ±0
  5. #170 Vuejs Skills 56.2 −0.2

Bars show each HVTrust score; the tick marks Claude Council’s 56.4.

Where the 56.4 comes from

HVTrust dimensions vs the Agent Skills average

56.4 / 100 · 100.0% confidence

Claude Council Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.4 / 25
in line with avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
1.7 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.0 above avg 14.0
AdoptionLog-scaled stars · package downloads
7.1 / 20
2.1 below avg 9.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-19
Rank Moved
Rank dropped 11 spots (#145 → #156)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
77.4
Activity sub-score · out of 100
#168

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-17 12:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-17

Activity & Reach

Stars
945
Forks
107
Last Push
2026-11-17
today
Commits (4 wk)
449
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #168

Analysis

Activity Inputs

77.4 / 100
StarsRepository reach
17.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
9.5 / 20

Common questions about Claude Council

Claude Council has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Claude Council publish package provenance?
No published build provenance is currently detected for Claude Council. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Claude Council have an OpenSSF Scorecard?
Claude Council has an OpenSSF Scorecard score of 6.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Claude Council actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Claude Council use?
Claude Council ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Claude Council's commits signed?
8% of the last 100 commits to Claude Council are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
6 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Claude Council's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, OpenRouter, Perplexity, xAI Grok
2026-09-02
Provider Added
Runtime surface grew — new detected provider dependency: OpenRouter

Maintain Claude Council?

For maintainers

HVTrust scores Claude Council from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 13HVTrust 3Surface 2Grade 1Scorecard 1Delisted 1Listed 1Surface 1
2026-10-19
Rank Moved
Rank dropped 11 spots (#145 → #156)
2026-09-25
Rank Moved
Rank dropped 12 spots (#138 → #150)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, OpenRouter, Perplexity, xAI Grok
2026-09-23
Rank Moved
Rank dropped 109 spots (#26 → #135)
2026-09-23
HVTrust Changed
HVTrust up 4.7pts (51.3 → 56.0)
2026-09-22
Newly Listed
First tracked at rank #26
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-07
Rank Moved
Rank rose 49 spots (#168 → #119)
2026-09-07
HVTrust Changed
HVTrust up 4.8pts (51.3 → 56.1)
2026-09-05
Rank Moved
Rank dropped 11 spots (#156 → #167)
2026-09-02
Provider Added
Runtime surface grew — new detected provider dependency: OpenRouter
2026-09-02
Rank Moved
Rank dropped 10 spots (#136 → #146)
2026-09-01
Rank Moved
Rank dropped 10 spots (#126 → #136)
2026-08-31
Rank Moved
Rank dropped 14 spots (#112 → #126)
2026-08-30
Rank Moved
Rank dropped 18 spots (#94 → #112)
2026-08-29
Rank Moved
Rank dropped 20 spots (#74 → #94)
2026-08-28
Rank Moved
Rank dropped 17 spots (#57 → #74)
2026-08-27
Rank Moved
Rank dropped 15 spots (#42 → #57)
2026-08-26
Scorecard Added
OSSF Scorecard: 4.1/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 91 spots (#133 → #42)
2026-08-26
HVTrust Changed
HVTrust up 32.1pts (18.9 → 51.0)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/claude-council.svg)](https://hvtracker.net/agents/claude-council)
HTML:
<a href="https://hvtracker.net/agents/claude-council"><img src="https://hvtracker.net/badge/claude-council.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON