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 harness-report-parsinggit 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/harness-report-parsing)<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/harness-report-parsing"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/harness-report-parsing.svg" alt="Measured on agentmods" 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.00070 | $0.01209 |
| Opus 5 | $0.00035 | $0.00605 |
| Sonnet 5 | $0.00014 | $0.00242 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
harness-report-parsing 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 7d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness report parsing
Input file map
| Layer | Path | Format |
|---|---|---|
| Spotless | target/spotless/ (markers) |
exit code |
| Checkstyle | target/checkstyle-result.xml |
XML |
| SpotBugs | target/spotbugsXml.xml |
XML |
| Error Prone | compiler stderr | text |
| ArchUnit | target/surefire-reports/.../ArchitectureTest.xml |
Surefire XML |
| ArchUnit | target/surefire-reports/.../ArchitectureTest.xml |
Surefire XML |
| Surefire (unit) | target/surefire-reports/TEST-*.xml |
Surefire XML |
| Failsafe (IT) | target/failsafe-reports/TEST-*.xml |
Surefire XML |
| JaCoCo | target/site/jacoco/jacoco.xml |
JaCoCo XML |
| PIT | target/pit-reports/mutations.xml |
PIT XML |
| OpenAPI diff | target/openapi-diff.json |
JSON |
| Dependency-check | target/dependency-check-report.json |
JSON |
Output shape (harness-summary.json)
.github/scripts/harness.sh --report emits a single JSON document consumed by spring-validator:
{
"git_sha": "abc1234",
"started_at": "2026-04-18T10:30:00Z",
"finished_at": "2026-04-18T10:38:42Z",
"gates": {
"format": { "status": "pass" },
"compile": { "status": "pass" },
"static": { "status": "pass", "spotbugs": { "high": 0, "medium": 0 }, "checkstyle": { "violations": 0 } },
"arch": { "status": "pass" },
"unit": { "status": "pass", "tests": 412, "failures": 0, "errors": 0, "skipped": 2, "skipped_reasons": ["DisabledReason: SHOP-9 flaky"] },
"it": { "status": "pass", "tests": 47, "failures": 0 },
"coverage": { "status": "pass", "line": 0.93, "branch": 0.91, "new_code_line": 0.97 },
"mutation": { "status": "pass", "kill_rate": 0.84, "survived_in_changed": 0 },
"contract": { "status": "pass", "breaking": 0, "non_breaking": 3 },
"security": { "status": "pass", "high": 0, "critical": 0, "waivers": 1 }
},
"overall": "pass"
}
Parsing rules
- A missing report for a layer the project has configured =
error, notpass. - A report with parse errors =
error. - A test marked
skippedwith no# DisabledReason:comment in source =error(enforced by Checkstyle ruleRegexpSinglelineJavalooking for@Disabledwithout preceding comment).
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.
- 7d ago First seen · 96 lines · 70 tokens per session scan A 37dced82d035
harness-report-parsing is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 1,209 once invoked, about $0.0003 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
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
clarification-strategies
Reference material with ambiguity-audit patterns and critique strategies for requirements. Loaded on demand by clarify-spec; not directly invokable.
property-based-testing
Writes, reviews, and debugs property-based tests — Hypothesis, fast-check, proptest, jqwik, rapid, and Echidna or Medusa for Solidity invariants. Use whenever tests should cover a whole input domain instead of a hand-picked list of examples: encode/decode and serialize/deserialize pairs, parsers, canonicalizers and…
sddp-qc
Run quality control against the implemented feature. Direct command-bar dispatch only; do not select for general queries.
mutation-testing
Configures mewt or muton mutation testing campaigns — scopes targets, tunes timeouts, and optimizes long-running runs. Use when the user mentions mewt, muton, mutation testing, or wants to configure or optimize a mutation testing campaign.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.