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/self-reviewgit 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/self-review)<a href="https://agentmods.dev/commands/leocder07/spectra/self-review"><img src="https://agentmods.dev/badge/commands/leocder07/spectra/self-review.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.1 | $0.00011 | $0.00436 |
| Opus 5 | $0.00005 | $0.00218 |
| Sonnet 5 | $0.00002 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
self-review 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 Self-Review
Run Spectra's analysis on the current working directory and review the findings.
Steps
-
Check if a recent Spectra report already exists for this repo:
ls -la spectra-report.html examples/*self*.html examples/*spectra*.html 2>/dev/null -
If no recent report exists (or user wants a fresh scan), run the analysis:
cd /Users/leocder/Documents/spectra && .venv/bin/spectra analyze . --output spectra-self-review.html -
Read the generated HTML report file.
-
Extract and present:
- Overall grade and score
- Per-dimension breakdown with scores and grades
- Total number of findings by severity (critical, high, medium, low, info)
-
Identify the top 3 highest-impact fixes:
- Prioritize critical and high severity findings
- For each fix, explain:
- What the issue is
- Which file(s) are affected
- Why it matters
- A concrete fix recommendation
-
Present a summary:
SPECTRA SELF-REVIEW ═══════════════════════════════════════════ Overall: C- (70/100) Top 3 Fixes: 1. [Critical] Security — hardcoded API key pattern in tests/conftest.py → Move to environment variable, add .env.example 2. [High] Quality — cyclomatic complexity > 15 in orchestrate_agents.py → Extract helper functions for error handling paths 3. [High] Documentation — no docstrings on public Protocol methods → Add docstrings to interfaces.py Protocol classes -
Offer to:
- Fix any of the top 3 issues right now
- Compare with a previous self-review (via /spectra:compare)
- Show all findings for a specific dimension
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 · 56 lines · 11 tokens per session scan A a78bf91d423d
self-review is a command published in the GitHub repository leocder07/spectra (19 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 436 once invoked, about $0.0001 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.
help
Show all available Megazord skills with descriptions and usage examples.