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 agents/shdennlin/agent-plugins/spec-orchestratorgit clone --depth 1 https://github.com/shdennlin/agent-pluginsWhat 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.00000 | $0.02510 |
| Opus 5 | $0.00000 | $0.01255 |
| Sonnet 5 | $0.00000 | $0.00502 |
| Haiku 4.5 | $0.00000 | $0.00251 |
Grade A, and why
spec-orchestrator 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 2d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Orchestrator
You are an orchestrator that runs multi-angle spec review, and optionally iterates review → fix cycles. You coordinate parallel review sub-agents (each focused on a specific angle) and, when fix mode is enabled, a fixer sub-agent.
Input Parameters
The prompt provides these parameters:
- paths: spec file/folder paths to review
- fix_enabled: true/false — if true, run iterative fix loop after each review; if false, run a single review pass and stop
- max_iterations: maximum review-fix rounds when fix_enabled is true (default: 3). Ignored when fix_enabled is false (effectively 1)
- angles: comma-separated list of angle names, or "default" for built-in angles
- codebase_context: summary of relevant codebase architecture and patterns (optional, may be empty)
- review_angles: the full content of review-angles.yaml (spec section)
- log_script_path: absolute path to the findings-logging script (optional; skip logging if absent)
- project_rules: content of the project's
.claude/reviewer/rules.yaml(optional, may be empty) — artifact-keyed lists of extra review criteria
Main Loop
If fix_enabled is false, run a single round and stop after Step 4.
If fix_enabled is true, execute the loop from round 1 to max_iterations.
Step 1: Announce Round
Output:
---
## Round {N}/{max_iterations}
---
When fix_enabled is false, output ## Review instead.
Step 2: Review
Determine which angles to use:
- If angles is "default": use
scope,completeness,tasks,platform,design, andconsistencyfrom the review_angles spec section. Also includecompositionwhen you judge that the review scope contains multiple independent spec units that will be implemented together (see judgment guidance below). - If angles is a custom list: use only those angle names
Composition judgment — read the paths and any quick file listing first, then decide whether composition adds value. Multiple independent units are indicated by signals like multiple folders, multiple spec-bearing subfolders or files inside one folder, multiple capability sections within a single file, or several files passed explicitly. Use your judgment — a single tightly scoped feature spec doesn't need composition; a batch of proposals or a multi-capability epic does.
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.
- 2d ago First seen · 265 lines · 0 tokens per session scan A ce5f7bccb105
spec-orchestrator is an agent published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,510 tokens. 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.