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 AdamBien/airails --skill sbcegit clone --depth 1 https://github.com/AdamBien/airailsWrote 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/adambien/airails/sbce)<a href="https://agentmods.dev/skills/adambien/airails/sbce"><img src="https://agentmods.dev/badge/skills/adambien/airails/sbce/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/adambien/airails/sbce"><img src="https://agentmods.dev/badge/skills/adambien/airails/sbce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00215 | $0.04806 |
| Opus 5.5 | $0.00086 | $0.01922 |
| Sonnet 5.5 | $0.00043 | $0.00961 |
| Haiku 4.5 | $0.00021 | $0.00481 |
Grade A, and why
sbce 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 today.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drive the spec-driven BCE workflow — one skill owns both the rules and the steps. Invoke as
/sbce <mode> <capability> (new or apply), or let it trigger from intent. Apply every rule
strictly.
Guiding principles
- The spec is the boundary contract — what the boundary promises, never how.
- The spec lives in the BC's package doc —
package-info.java(Java,///Markdown) orpackage-info.md(web) — co-located with the code it governs. There is no separatespecs/tree and no hand-typed package coordinate. In Java the///doc renders viajavadoc, so the same file is source-of-truth and published contract. - One capability spec ≡ one business component, named the same. No translation between "what" and "where".
- The task list is the gap, read off
specvsBCon demand — never a hand-maintained tasks file. - One spec per capability, the single source of truth — never diff or merge two specs.
- Split by determinism: tooling runs tests and places the BC; this skill writes the spec, the code, and closes the gap.
- "Done" is a green run of the stack's test loop — never your own opinion.
Spec ↔ BC mapping
The BC name is the only identity — a single lowercase token (checkout), never a dotted path
or a bc/capability field. The stack skill owns where it lands:
checkout # BC name == the only identity
spec = package doc, co-located with code:
Java: src/main/java/<base>/checkout/package-info.java # `///` Markdown (JEP 467)
web: app/src/checkout/package-info.md # Markdown
code = same folder, {boundary,control,entity}/ # stack skill places it
## Boundaryop ↔ oneboundaryentry-point method.## Requirements(EARS) ↔ behaviour and the tests covering it.## Entities↔ theentitylayer.
System doc (base package)
An optional doc one altitude up — the base package's package-info.java /
app/src/package-info.md — for concerns that span BCs and have no other home. Add a section
only when a real cross-BC concern appears; a one-BC system needs none. Author from
references/system-doc-template.md.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +1 lines adf582a2a844
- 23d ago Changed · +14 lines 2673c0a6d1fd
- 24d ago Changed · +1 lines a16d865f7317
- 1mo ago First seen · 183 lines · 215 tokens per session scan A 2e20a87d0b33
sbce is a skill published in the GitHub repository AdamBien/airails (59 stars, last pushed yesterday), licensed MIT. It adds 215 tokens to every session and 4,806 once invoked, about $0.0009 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
simulation-validator
Validate simulations across three stages — run pre-flight checks on configuration files (parameter ranges, required fields, disk space), monitor runtime logs for residual growth, NaN/Inf, and adaptive dt collapse, and perform post-flight validation of results (physical bounds, mass/energy conservation, convergence).…
skill-evaluator
Rigorously evaluate an Agent Skill end-to-end across ANY coding-agent CLI — verify its scripts emit the documented numbers (deterministic checks), test whether its description triggers on the right prompts, and measure whether an agent following the SKILL.md beats a no-skill baseline (with/without pass-rate delta…
unit-test-parameterized
Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource. Creates tests that run the same logic with multiple input values. Use when writing data-driven Java tests, multiple test cases from single method, or boundary value…
unit-test-scheduled-async
Provides patterns for unit testing Spring @Scheduled and @Async methods using JUnit 5, CompletableFuture, Awaitility, and Mockito. Covers mocking task execution and timing, verifying execution counts, testing cron expressions, validating retry behavior, and simulating thread pool behavior. Use when testing background…
unit-test-mapper-converter
Provides patterns for unit testing mappers, converters, and bean mappings. Validates entity-to-DTO and model transformation logic in isolation. Generates executable mapping tests with MapStruct and custom converter test coverage. Use when writing mapping tests, converter tests, entity mapping tests, or ensuring…
unit-test-service-layer
Provides patterns for unit testing service layer with Mockito. Creates isolated tests that mock repository calls, verify method invocations, test exception scenarios, and stub external API responses. Use when testing service behaviors and business logic without database or external services.