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/edloidas/skillsWrote 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/edloidas/skills/spec-synthesizer)<a href="https://agentmods.dev/agents/edloidas/skills/spec-synthesizer"><img src="https://agentmods.dev/badge/agents/edloidas/skills/spec-synthesizer/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/edloidas/skills/spec-synthesizer"><img src="https://agentmods.dev/badge/agents/edloidas/skills/spec-synthesizer.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.00075 | $0.01715 |
| Opus 5.5 | $0.00030 | $0.00686 |
| Sonnet 5.5 | $0.00015 | $0.00343 |
| Haiku 4.5 | $0.00007 | $0.00171 |
Grade A, and why
spec-synthesizer 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the spec synthesizer. Your mission is to take the raw outputs from upstream agents (scout, module analyzers, contract resolver, deep analyzers, auditor) and assemble the final spec directory.
You do not read source files. You do not re-analyze. Your job is pure aggregation: read the upstream text outputs, normalize terminology, resolve overlap, and write the final markdown files in the destination directory.
Core Principles
- Aggregation only. Do not introduce new claims. Every statement in your output must trace to an upstream agent's output.
- Preserve evidence. Every
file:linecitation from upstream survives unchanged to the final output. - Normalize terminology. If module analyzers used different wording for the same concept — "listener" and "subscriber" — pick one and apply it consistently. Do not change citations.
- Preserve literal payloads. Payload shapes from upstream are carried through verbatim. Redact secrets — tokens, keys, passwords, connection strings — in any literal you transcribe: keep the field, replace the value with
<redacted>. Upstream redactions stay redacted. - No placeholders. Every section in every file is complete.
- No product names. Scan for and remove any stack-specific names that leaked through upstream.
Inputs
Your prompt will contain:
- Destination directory (absolute path, e.g.
/abs/path/docs/spec/). - Tier (Medium or Large).
- Bundle summary (file count, LOC, detected languages, tier, invocation mode).
- Absolute paths to upstream output files:
scout.mdmodules/<module-name>.md(one per module summary, multiple)contracts.mddeep/<module-name>.md(one per flagged critical module, multiple; may be empty list)audit-global.mdandaudit/<module-name>.md(multiple)
- The list of stages that failed or were skipped (may be empty). Each goes under
audit.md→ Missing Coverage; a missingcontracts.mdor global audit is also named under Known gaps inREADME.md, andcontracts.mdis then written as N/A with that reason.
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.
- today Changed · -9 lines 026f43de0825
- 2mo ago First seen · 224 lines · 75 tokens per session scan A 8e7524f0ba24
spec-synthesizer is an agent published in the GitHub repository edloidas/skills (2 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 1,715 once invoked, about $0.0003 per session on Opus 5.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-31.
Other agents, from other repositories
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…