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/analyzegit clone --depth 1 https://github.com/leocder07/spectraWhat 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.00018 | $0.00268 |
| Opus 5 | $0.00009 | $0.00134 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
analyze 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 3d 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 Analyze
Run the full Spectra analysis pipeline on the repository at "$ARGUMENTS".
Steps
-
Run the analysis using the Bash tool:
cd /Users/leocder/Documents/spectra && .venv/bin/spectra analyze $ARGUMENTS -
If the command succeeds, read the generated HTML report file and summarize:
- Overall grade and score
- Top 3-5 critical or high-severity findings
- Dimension breakdown (Architecture, Security, Quality, Documentation, Maintainability, Performance)
-
If the command fails, explain the error using Spectra error codes:
- SPEC-001: Git clone failed — check the repository URL
- SPEC-002: API unreachable — check ANTHROPIC_API_KEY
- SPEC-003: Rate limited — wait and retry
- SPEC-004: Token budget exceeded — try a smaller repo or --quick
- SPEC-006: Agent timeout — try --quick flag
-
After analysis, offer to:
- Open the HTML report in browser
- Explain specific findings in detail
- Suggest fixes for critical issues
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.
- 3d ago First seen · 32 lines · 18 tokens per session scan A e211e32ef52b
analyze is a command published in the GitHub repository leocder07/spectra (19 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 268 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.
go
Execute the current phase plan with subagent delegation.