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 skills/loiane/specs-driven-development-spring-angular/archunit-rulesnpx skills add loiane/specs-driven-development-spring-angular --skill archunit-rulesgit 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.00033 | $0.01146 |
| Opus 5 | $0.00016 | $0.00573 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
archunit-rules 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchUnit rules
Default rule set (greenfield)
These rules assume package-by-feature with typed sub-packages
(see spring-boot-4-conventions): each top-level package under the application
root is a feature/domain with an api (published) sub-package and private
impl sub-packages (internal/, model/, repository/, service/).
There are no top-level controller / service / repository packages.
Place these in src/test/java/.../arch/ArchitectureTest.java:
@AnalyzeClasses(packages = "com.example.shop", importOptions = ImportOption.DoNotIncludeTests.class)
class ArchitectureTest {
// Other features depend only on a feature's api package, never on its private impl packages.
@ArchTest
static final ArchRule internalIsPrivateToItsFeature =
slices().matching("com.example.shop.(*)..")
.should().notDependOnEachOther()
.ignoreDependency(
JavaClass.Predicates.resideInAPackage("..internal.."),
JavaClass.Predicates.resideInAPackage("..api.."));
// No class outside a feature may reach into its private sub-packages.
@ArchTest
static final ArchRule no_internal_access_across_features =
noClasses().that().resideOutsideOfPackages(
"..(*).internal..",
"..(*).model..",
"..(*).repository..",
"..(*).service..")
.should().dependOnClassesThat().resideInAnyPackage(
"..internal..",
"..model..",
"..repository..",
"..service..");
@ArchTest
static final ArchRule no_field_injection =
noFields().should().beAnnotatedWith("org.springframework.beans.factory.annotation.Autowired");
// Forbid by-layer packages at the application root level only.
@ArchTest
static final ArchRule no_by_layer_root_packages =
noClasses().should().resideInAnyPackage(
"com.example.shop.controller..",
"com.example.shop.service..",
"com.example.shop.repository..",
"com.example.shop.model..",
"com.example.shop.dto..",
"com.example.shop.util..");
// Entities must live in a feature's model or internal sub-package (never at root or in api).
@ArchTest
static final ArchRule entities_in_feature_private_package =
classes().that().areAnnotatedWith("jakarta.persistence.Entity")
.should().resideInAnyPackage("..internal..", "..model..");
@ArchTest
static final ArchRule no_cycles_between_features =
slices().matching("com.example.shop.(*)..").should().beFreeOfCycles();
}
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 · 121 lines · 33 tokens per session scan A 180730e99fb6
archunit-rules is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,146 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 skills, from other repositories
test-writer
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines.
spec-kitty-implement-review
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…
spec-kitty-program-orchestrate
Orchestrate a multi-repo, multi-mission Spec Kitty program end-to-end: run specify → plan → tasks → implement → review → merge → mission-review → post-merge fixes across several repositories in a defined dependency order, using background sub-agents for parallel work and a pulse-heartbeat safety net for long…
spec-kitty-runtime-next
Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…
spec-kitty-bulk-edit-classification
Recognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y feature", "sed everywhere", or any request…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…