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.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.00075 | $0.01741 |
| Opus 5 | $0.00037 | $0.00870 |
| Sonnet 5 | $0.00015 | $0.00348 |
| Haiku 4.5 | $0.00007 | $0.00174 |
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 224 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, pick one and apply it consistently. Do not change citations.
- Preserve literal payloads. Payload shapes from upstream are carried through verbatim.
- 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)
Workflow
Step 1: Read all upstream outputs
Use Read on every upstream file listed in your prompt.
Step 2: Plan the output directory
Files to create in the destination:
README.md— bundle summary, tier, how to read the spec.architecture.md— derived from scout output.modules.md— module catalog table + per-module medium-depth summaries.contracts.md— derived from contract resolver output.audit.md— consolidated audit findings (global + per-module).modules/<module-name>.md— for each flagged critical module, the deep 11-section spec.
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.
- 8d 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 yesterday), licensed MIT. It adds 75 tokens to every session and 1,741 once invoked, about $0.0004 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-31.
Other agents, from other repositories
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
code-reviewer
Use this agent when you need to review code changes for correctness, discovered project-convention compliance, and duplicated logic. Invoke proactively after writing or modifying code, and before committing or opening a pull request. Reviews an explicit diff, pull request, or named file set; defaults to the…
issue-feature-review
Review GitHub feature requests with constructive skepticism. Summarize the ask, evaluate user impact and implementation cost, flag unknowns, and provide a recommendation with actionable next steps.
comment-analyzer
Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. Use cases include large documentation comments or docstrings, pull requests that add or modify comments, technical debt or comment rot review, and checks that comments match the code they describe.
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.
type-design-analyzer
Use this agent when you need expert analysis of type design in your codebase. Use cases include introducing a new type, reviewing all types added by a pull request, and refactoring existing types to improve their design quality. The agent provides qualitative feedback and quantitative ratings on encapsulation…