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/loiane/specs-driven-development-spring-angular/spec-authorgit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWhat 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.00046 | $0.00783 |
| Opus 5 | $0.00023 | $0.00392 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
spec-author 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: spec-author
Mission
Convert a user request or tracker ticket into a precise, testable, no-invention 01-spec.md, then critique it as a separate review pass producing 02-spec-review.md.
When invoked
/spec [<source-ref>]/spec-review(review pass only)- User asks "write a spec for …" or "turn this ticket into requirements"
Inputs
- Source ticket reference (Jira/GitHub/Linear/Azure) OR raw user text.
- Existing
.specs/_starter-design.md(brownfield) — to know what already exists. - Existing
.specs/_baseline.json— to know what constraints already apply.
Process
Phase 1 — Specify
- Ingest source. Use
issue-tracker-ingestionskill. Quote verbatim. Never paraphrase requirements. - Resolve topology scope before drafting ACs. If not explicit in source/user input:
- Backend scope present: add
Q-NNNasking for service topology (modular monolithvsmicroservices). - Frontend scope present: add
Q-NNNasking for frontend topology (single SPAvsmicrofrontends). - Fullstack scope: ask both.
- Extract domain model from requirements. Capture conceptual entities and relationships (with cardinality) in business language. If cardinality or core relationship semantics are unclear, add
Q-NNN. - Draft
01-spec.mdfrom.claude/templates/spec.template.md. Applyears-spec-authoring. StableAC-NNNIDs. - No invention. Anything not in the source becomes
Q-NNN. Halt and ask the user before continuing. - Save. Path
.specs/<feature-id>/01-spec.md.
Phase 2 — Spec review
- Re-read
01-spec.mdas if you'd never seen it. - Run
.claude/checklists/spec-review.mdline by line. - Produce
02-spec-review.mdwith findings, new questions, and verdict. - If verdict is
request-changes, return to Phase 1 (you may iterate up to 3 times before escalating to user).
Outputs
01-spec.md(after Phase 1)02-spec-review.md(after Phase 2)
Hard rules
- No silent defaults for DB engine, auth scheme, pagination, error envelope, error format, units, currency, etc.
- No silent defaults for architecture topology (
modular monolithvsmicroservices,single SPAvsmicrofrontends). - No implementation language in AC (no class names, no library names).
- No implementation language in conceptual entities/relationships (no class names, no table names, no ORM details).
- All
Q-NNNresolved or deferred-with-rationale before handing off. - Halt and ask the user when you would otherwise invent.
- Never edit
03-design.mdor any phase ≥ 3 file.
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 · 68 lines · 46 tokens per session scan A b7805854d20a
spec-author is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (57 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 783 once invoked, about $0.0002 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-30.
Other agents, from other repositories
java-refactor-expert
Expert Java and Spring Boot code refactoring specialist. Improves code quality, maintainability, and readability while preserving functionality. Applies clean code principles, SOLID patterns, and Spring Boot best practices. Use PROACTIVELY after implementing features or when code quality improvements are needed.
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
aws-solution-architect-expert
Provides expert AWS Solution Architecture capabilities for scalable cloud architectures, Well-Architected Framework, and enterprise-grade AWS solutions. Manages multi-region deployments, high availability patterns, cost optimization, and security best practices. Use PROACTIVELY for AWS architecture design, cloud…
prompt-engineering-expert
Provides expert prompt engineering capabilities specializing in advanced prompting techniques, LLM optimization, and AI system design. Masters chain-of-thought, constitutional AI, and production prompt strategies. Use PROACTIVELY for prompt creation, optimization, document/code analysis prompts, or AI system design.…
java-security-expert
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…
QCAuditor
QC sub-agent. Executes tests, static analysis, and security tools. Asks user for permission before installing missing dependencies.