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 skills add loiane/specs-driven-development-spring-angular --skill spring-security-baselinegit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWrote 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/skills/loiane/specs-driven-development-spring-angular/spring-security-baseline)<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/spring-security-baseline"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/spring-security-baseline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/spring-security-baseline"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/spring-security-baseline.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.00917 |
| Opus 5.5 | $0.00015 | $0.00367 |
| Sonnet 5.5 | $0.00008 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
spring-security-baseline 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Security baseline
What every endpoint must declare
In 03-design.md, for each new/changed endpoint:
- AuthN: Anonymous? Bearer (JWT)? Session? mTLS?
- AuthZ: What role/scope/claim is required?
- Input validation: Bean Validation on the DTO (
@NotNull,@Size,@Pattern, …) PLUS service-layer invariants. - Output: Does the response include any field the caller is not allowed to see?
- Audit: Should this action be logged with structured fields (
actor,subject,outcome)?
If any of these is unclear, write a Q-NNN — do not pick a default.
Default SecurityFilterChain (resource server, JWT)
@Configuration
@EnableWebSecurity
@EnableMethodSecurity
class SecurityConfig {
@Bean
SecurityFilterChain api(HttpSecurity http) throws Exception {
http
.securityMatcher("/api/**")
.authorizeHttpRequests(a -> a
.requestMatchers("/api/public/**").permitAll()
.anyRequest().authenticated())
.oauth2ResourceServer(o -> o.jwt(Customizer.withDefaults()))
.csrf(csrf -> csrf.disable()) // stateless API
.sessionManagement(s -> s.sessionCreationPolicy(STATELESS))
.headers(h -> h
.contentSecurityPolicy(c -> c.policyDirectives("default-src 'none'"))
.referrerPolicy(r -> r.policy(STRICT_ORIGIN_WHEN_CROSS_ORIGIN)));
return http.build();
}
}
CSRF is disabled only for stateless APIs. If sessions are used, CSRF is on.
Method-level authorization
Prefer @PreAuthorize with SpEL using JWT claims:
@PreAuthorize("hasAuthority('SCOPE_orders:write') and #orderId == authentication.token.claims['order_id']")
public Order apply(@PathVariable UUID orderId, @Valid @RequestBody ApplyGiftCardRequest req) { ... }
Secrets
- Never commit secrets. Use environment variables or a secrets manager.
application.ymlreferences${VAR}; absence fails fast at startup.- Tests use Testcontainers; secrets there are throwaway.
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.
- 1mo ago First seen · 95 lines · 38 tokens per session scan A 3af7675522eb
spring-security-baseline is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 13d ago), licensed MIT. It adds 38 tokens to every session and 917 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
spec-kitty-orchestrator-api-operator
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers: "use orchestrator-api", "build a custom orchestrator", "automate externally", "integrate CI with spec-kitty", "call spec-kitty from another tool", "orchestrator contract", "external…
spk-integrate-orchestrator-api
Use Spec Kitty orchestrator-api from external systems, respecting host boundaries, state contracts, and workflow commands.
806-regulations-eu-data-act
Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls. This should…
123-java-design-patterns
Use when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven patterns, database and persistence patterns, and cross-cutting integration patterns. This should trigger for requests such as Apply Java design…
125-java-concurrency
Use when you need to apply Java concurrency best practices — including thread safety fundamentals, ExecutorService thread pool management, concurrent design patterns like Producer-Consumer, asynchronous programming with CompletableFuture, immutability and safe publication, deadlock avoidance, virtual threads…
302-frameworks-spring-boot-rest
Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the…