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.
git 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/commands/loiane/specs-driven-development-spring-angular/wire-harness)<a href="https://agentmods.dev/commands/loiane/specs-driven-development-spring-angular/wire-harness"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/wire-harness/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/commands/loiane/specs-driven-development-spring-angular/wire-harness"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/wire-harness.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.00022 | $0.01805 |
| Opus 5.5 | $0.00009 | $0.00722 |
| Sonnet 5.5 | $0.00004 | $0.00361 |
| Haiku 4.5 | $0.00002 | $0.00180 |
Grade A, and why
wire-harness 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wire-harness
Phase: 0 (meta) — onboarding extension
Owning agent: .claude/agents/spring-onboarding.md
Skills used: maven-harness-pom, jacoco-coverage-policy, pit-mutation-tuning, flyway-or-liquibase-detection, harness-report-parsing
Purpose
Wire the Maven harness layers (Spotless, Checkstyle, SpotBugs, Surefire/Failsafe split, JaCoCo, PIT, OWASP Dependency-Check) plus the chosen migration tool dependency into a Maven module's pom.xml. Runs against a module that has already been classified by /onboard so that subsequent /spec → /plan → /build cycles execute against fully gated quality bars from day one.
This command exists because /onboard Process step 4 says "add missing harness layers" but only on the POM-and-config surface, while /build is strictly TDD and refuses to edit the POM without a <task-id> in flight. /wire-harness fills that gap.
Inputs
None required. Optional argument: a path to a Maven module (default .). For polyglot monorepos pass the module directory (e.g. shoply-api).
Reads
- The target module's
pom.xml. .specs/_stack.json(must exist — produced by/onboard)..specs/_onboarding.mdand.specs/_known-debt.md(to know what's already accepted as deferred)..specs/adr/(must already contain the migration-tool decision if the module uses a database)..claude/maven/parent-pom-fragment.xmland.claude/skills/maven-harness-pom/SKILL.md(authoritative reference)..claude/skills/jacoco-coverage-policy/SKILL.md,.claude/skills/pit-mutation-tuning/SKILL.md,.claude/skills/flyway-or-liquibase-detection/SKILL.md.
Writes
<module>/pom.xml(plugin and dependency wiring; properties block; profile blocks).<module>/checkstyle.xml(starter Google-style config if missing).<module>/dependency-check-suppressions.xml(empty suppression file if missing)..specs/_baseline.json(refreshed via.github/scripts/harness.sh --baselineafter the wiring run)..specs/_stack.json(refreshed via.github/scripts/detect-stack.sh)..specs/_known-debt.md(close the harness debt entry; add new entries for any layer deferred during this pass with rationale and trigger)..specs/_starter-design.md(record chosen profiles, code style, naming conventions for unit/IT tests)..specs/adr/ADR-NNN-*.md(one ADR per deferred layer that overrides a default inmaven-harness-pom).
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 · 72 lines · 22 tokens per session scan A 01e21043a461
wire-harness is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 1,805 once invoked, about $0.0001 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 commands, from other repositories
spec-impl
Execute spec tasks using TDD methodology.
benchmark
Design and coordinate a reproducible Java performance test.
profile
Coordinate a reproducible Java profiling and optimization lifecycle.
update-issue
Update an issue description with structured, evidence-backed content.
create-diagram
Create an architecture or design diagram from selected source artifacts.
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.