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 commands/leocder07/spectra/leaderboardgit clone --depth 1 https://github.com/leocder07/spectraWrote 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/commands/leocder07/spectra/leaderboard)<a href="https://agentmods.dev/commands/leocder07/spectra/leaderboard"><img src="https://agentmods.dev/badge/commands/leocder07/spectra/leaderboard.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.00007 | $0.00441 |
| Opus 5 | $0.00003 | $0.00220 |
| Sonnet 5 | $0.00001 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
leaderboard 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 5d 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.
What it actually says
Spectra Leaderboard
Compare code health scores across all analyzed repositories.
Steps
-
Find all Spectra report files in the
examples/directory:Look for *.html files that contain Spectra report data (grade-gauge, dim-score elements) -
For each report file, extract:
- Repository name (from the
<title>tag: "Spectra Report — {name}") - Overall grade and score (from
.grade-gauge-letterand.grade-gauge-score) - Per-dimension scores: Architecture, Security, Quality, Documentation, Maintainability, Performance
(from
.dim-scoreand.dim-gradeelements paired with.dim-label) - Total finding count (sum the numbers in
<h2>Dimension (N)</h2>headers)
- Repository name (from the
-
Present a comparison table sorted by overall score (highest first):
SPECTRA LEADERBOARD ═══════════════════════════════════════════════════════════════════════ Repo Overall Arch Sec Qual Docs Maint Perf Findings ─────────────────────────────────────────────────────────────────────── flask A- (87) 91 A 83 B+ 90 A 86 B+ 87 A- 83 B 59 express B- (80) 89 A- 67 D+ 87 B+ 68 C- 92 A 76 C+ 46 spectra C- (70) 84 B+ 67 C- 62 D 65 D+ 68 C- 62 D 54 -
Highlight:
- Best and worst scores per dimension
- Common weak areas across repos
- Which repos lead in each dimension
-
Offer to:
- Show detailed findings for any specific repo
- Open the leaderboard HTML page (
examples/leaderboard.html) in a browser - Run a new analysis to add another repo to the comparison
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.
- 5d ago First seen · 44 lines · 7 tokens per session scan A 03f50a675592
leaderboard is a command published in the GitHub repository leocder07/spectra (19 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 441 once invoked, about $0.0000 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.
Other commands, from other repositories
run
Run an Exolvra Genesis loop — builder subagents iterate against blind, fresh-context critics comparing real output to a concrete quality bar, until the assembled work wins twice in a row. Takes a one-line goal or a path to an existing spec.
interview
Interview your way to an Exolvra Genesis-ready spec and a single-file interactive mockup — or modify an existing pair. Ends with the exact /exolvra-genesis:run line to fire.
update
Update Megazord to the latest version.
debug
Systematic four-phase debugging (reproduce, isolate, root-cause, fix).
discuss
Socratic brainstorming to explore approaches before implementation.
go
Execute the current phase plan with subagent delegation.