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/spring-onboardinggit 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.00037 | $0.01132 |
| Opus 5 | $0.00018 | $0.00566 |
| Sonnet 5 | $0.00007 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
spring-onboarding 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: spring-onboarding
Mission
Bootstrap an existing Spring codebase into the spec-driven workflow without blocking day one. Produce repo-wide artifacts (.specs/_*) that subsequent feature work consults.
When invoked
/onboard- First time the toolkit is run on a repo with no
.specs/folder.
Process
-
Detect the stack. Resolve the Maven module path (optional
/onboard <path>argument; default.). Run.github/scripts/detect-stack.sh "$MODULE/pom.xml" > .specs/_stack.json. Record Java version, Spring Boot version, DB engine, migration tool, test stack, build tool, OpenAPI presence, and any sibling non-JVM apps (e.g. Angular/React frontend) detected undersiblings. Refuse to proceed if Flyway and Liquibase are both present (bothis fatal). -
Run the harness in baseline mode (brownfield only — skip for greenfield modules).
./.github/scripts/harness.sh --module "$MODULE" --baseline > .specs/_baseline.jsonCapture: Checkstyle violations, SpotBugs by severity, JaCoCo line/branch overall and per-package, PIT kill rate (incremental scope), ArchUnit violations, OpenAPI presence, Dependency-Check High/Critical counts.
-
Add missing harness layers to
pom.xmlpermaven-harness-pom:- JaCoCo
<minimum>set to current minus 1% (ratchet). - PIT in
pitprofile,+GIT(from[origin/main])scope. - ArchUnit rules added with
FreezingArchRule.freeze(...)for existing violations. - Spotless with
<ratchetFrom>origin/main</ratchetFrom>.
- JaCoCo
-
Generate
.specs/_starter-design.mddescribing the codebase as it actually is: top-level packages, dominant patterns (constructor vs field injection,@RestControllervs@Controller, RestTemplate vs RestClient), how it currently does auth, error handling, observability. This becomes the reference for "what's normal here". -
Run frontend baseline checks when a sibling frontend app exists (e.g. an Angular app detected in
siblings): run lint, test, and build for that app, or explicitly report any missing scripts.
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 · 79 lines · 37 tokens per session scan A 201c855684ae
spring-onboarding is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,132 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.