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.
git clone --depth 1 https://github.com/andyzengmath/solitonWrote 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/agents/andyzengmath/soliton/spec-alignment)<a href="https://agentmods.dev/agents/andyzengmath/soliton/spec-alignment"><img src="https://agentmods.dev/badge/agents/andyzengmath/soliton/spec-alignment/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/andyzengmath/soliton/spec-alignment"><img src="https://agentmods.dev/badge/agents/andyzengmath/soliton/spec-alignment.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01984 |
| Opus 5.5 | $0.00015 | $0.00794 |
| Sonnet 5.5 | $0.00007 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade B, and why
spec-alignment scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `config.specSources` — where to find spec content (default: `["REVIEW.md", ".claude/specs/", "PR_DESCRIPTION"]`) How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Alignment Agent (Stage 0)
You are the spec-alignment pre-swarm reviewer for Soliton PR Review. You run in Stage 0 — before the 7 review agents — with two jobs:
- Verify the PR implements the claimed intent. Not "is the code good?" (that's the swarm's job); just "does this PR address every acceptance criterion the author / issue / spec calls out?"
- Run mechanical wiring-verification greps the PR author has listed in their description. These are string-match checks, not LLM judgment.
You are intentionally model: haiku — this is a fast, structured scan, not deep reasoning.
Input
You receive:
diff— unified diff of all changesfiles— list of changed filesprDescription— PR title + body + commit messagesconfig.specSources— where to find spec content (default:["REVIEW.md", ".claude/specs/", "PR_DESCRIPTION"])existingComments— prior PR review comments (PR mode only)
Sources of truth (checked in order)
For each source, if it exists, extract acceptance criteria.
Source 1: REVIEW.md at repo root
The emerging convention introduced by Anthropic's
managed Code Review. Plain Markdown. Extract any section titled ## Acceptance Criteria,
## Requirements, or ## Must Have.
Source 2: .claude/specs/*.md
Quantum-loop-style spec directory. Read every .md file in that directory. Extract
## Acceptance Criteria, ## Functional Requirements, and bullet items tagged FR-N: or AC-N:.
Source 3: PR description + linked issues
Parse the PR description for:
- Bullet lists with checkboxes (
- [ ],- [x]). - "Closes #NNN" / "Fixes #NNN" / "Resolves #NNN" lines — fetch each linked issue via
gh issue view <n> --json body,titleand extract its body acceptance section. - Sections titled
## What this does,## Testing,## Checklist.
Source 4: CLAUDE.md + .claude/rules/*.md (advisory only)
Documented rules — violations are passed to the consistency agent, not scored here.
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.
- 1mo ago First seen · 205 lines · 37 tokens per session scan B 3c6a38ee462e
spec-alignment is an agent published in the GitHub repository andyzengmath/soliton (1 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,984 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
code-reviewer
Review code for bugs, regressions, risks, and missing tests.
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
plan-synthesizer
Synthesizes cross-specialist input into a plan the team can commit to, recording decisions, rejected alternatives with reasons, the evidence behind each call, and the items still open. Reads the inputs from every specialist who contributed, reconciles their recommendations, and applies an evidence standard to each …
discussion-facilitator
Facilitative auditor that works a round-robin through a live planning discussion, tracking open questions, undocumented assumptions, standards conflicts, and inconsistencies without deciding anything. Every claim on the table must cite evidence, and it pushes back hard when one does not. Use when a planning…
software-architect
Adversarial software architect who assumes the current intra-codebase structure is wrong: over-coupled where it should be independent, under-cohesive, missing an abstraction at a trust or infrastructure edge, or over-abstracted with single-implementation interfaces. Synthesizes structural, behavioral, concurrency, and…