Citadel
The operating layer for Claude Code + OpenAI Codex: persistent project memory, intent routing, safety hooks, cost telemetry, and parallel agent fleets.
Is Citadel safe? Promising trust profile, but some evidence still deserves review.
Compare Citadel
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Citadel scores 63.1/100 (Grade C), ranked #74 of 351 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 7.2/10; 50% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Citadel compares in Agent Skills
- #72 Deepchat 63.4 +0.3
- #73 Ui Ux Pro Max Skill 63.4 +0.3
- #74 Citadel 63.1 this agent
- #75 Skills For Humanity 62.9 −0.2
- #76 Drama Skills 62.8 −0.3
Bars show each HVTrust score; the tick marks Citadel’s 63.1.
Where the 63.1 comes from
HVTrust dimensions vs the Agent Skills average
63.1 / 100 · 100.0% confidenceCitadel Agent Skills average (351 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
74.9 / 100Supply Chain Trust
Common questions about Citadel
Does Citadel publish package provenance?
Does Citadel have an OpenSSF Scorecard?
Is Citadel actively maintained?
What license does Citadel use?
Are Citadel's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Citadel'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.
Maintain Citadel?
For maintainers
HVTrust scores Citadel 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/citadel)
<a href="https://hvtracker.net/agents/citadel"><img src="https://hvtracker.net/badge/citadel.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON