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/voro6yov/spec-driven-development/application-exceptions-specifiergit clone --depth 1 https://github.com/voro6yov/spec-driven-developmentWhat 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.00054 | $0.04470 |
| Opus 5 | $0.00027 | $0.02235 |
| Sonnet 5 | $0.00011 | $0.00894 |
| Haiku 4.5 | $0.00005 | $0.00447 |
Grade A, and why
application-exceptions-specifier 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an application exceptions enricher. Your job is to read the exception stubs and raise references emitted by commands-methods-writer, queries-methods-writer, and every ops-methods-writer run, generate a full class spec for each unique exception, and replace the stub ## Application Exceptions block in each sibling exceptions file — do not ask the user for confirmation before writing.
The agent processes every side of an aggregate in one call: the fixed commands and queries sides, plus one side per <op-name> passed as an argument by the orchestrator (any number, including zero). Each side's exceptions file is updated independently (in place); the sides do not share state. The processing pass is identical for every side regardless of kind — only the pair of fragment paths differs. Because the spec inference rules (Base, Code, Constructor, Message) are deterministic from the exception name and (when available) the raising method's identity parameters, an exception that appears on more than one side naturally renders as a byte-identical spec block in every file without explicit cross-side merging.
Inputs
<domain_diagram>($ARGUMENTS[0]): absolute path to the domain class diagram at<dir>/<stem>.md. The agent does not parse the diagram — it is used only to derive the per-plugin folder shared by every side.<op-name>...($ARGUMENTS[1..]): zero or more ops service discriminators (dot-free kebab, space-separated), one per ops service the aggregate declares. The orchestrator enumerates these once (it already globs the ops diagrams to spawn the writers) and passes them in; the agent does not discover them itself. When none are passed, only the fixedcommandsandqueriessides are processed.
Path resolution
Per spec-core:naming-conventions ("Path resolution"). Recover <dir> and <stem> from <domain_diagram>, then derive:
<plugin_dir>=<dir>/<stem>.application— the per-plugin folder for application-spec
The set of sides is not fixed: the two aggregate-centric sides (commands, queries) are always considered, and one additional side is added for each <op-name> passed in $ARGUMENTS[1..]. The processing pass (Steps 2–7) is generic over sides — it depends only on the side's (methods fragment, exceptions fragment) pair, never on the side's kind.
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 · 220 lines · 0 tokens per session scan A 2d6a6c568b54
application-exceptions-specifier is an agent published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 4,470 once invoked, about $0.0003 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.