Borrowing it
Nothing to install: this file belongs to AURORA-NEURO/aurora-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AURORA-NEURO/aurora-agent/main/.agents/skills/measure-section-boilerplate/SKILL.mdgit clone --depth 1 https://github.com/AURORA-NEURO/aurora-agentWrote 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/aurora-neuro/aurora-agent/measure-section-boilerplate)<a href="https://agentmods.dev/skills/aurora-neuro/aurora-agent/measure-section-boilerplate"><img src="https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/measure-section-boilerplate/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/aurora-neuro/aurora-agent/measure-section-boilerplate"><img src="https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/measure-section-boilerplate.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.00071 | $0.02102 |
| Opus 5 | $0.00036 | $0.01051 |
| Sonnet 5 | $0.00014 | $0.00420 |
| Haiku 4.5 | $0.00007 | $0.00210 |
Grade A, and why
measure-section-boilerplate 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 11d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Measure section boilerplate
Sections of this blueprint are heavily repetitive. §42 carries about five distinguishing lines per module; §23 carries about fifty-four. That difference is the whole reason a coverage percentage is not a progress bar — twenty modules of one section are not twenty modules of another — so every crate that builds against a section is expected to measure it.
Agents measuring the same section have disagreed three times. Every disagreement was run down to
a specific unstated definition, and none was a mistake. The resolutions are in docs/COVERAGE.md
under "Three disagreements, three distinct causes". Read them before you measure, because you are
about to make the same three choices.
State the method before the number
A percentage with no method attached is not reproducible and will start a fourth disagreement. State
all six of these, every time. crates/megafactory/src/lib.rs and crates/sweep/src/lib.rs are the
worked examples.
- Corpus — which files. Exclude
00_SECTION_INDEX. Say the count. - Unit — line, heading-block, or character.
- Normalisation — trailing whitespace trimmed, and anything else you did.
- Threshold — a line is shared when it occurs in at least k of n modules. Give k.
- Blank lines — in or out.
- YAML front matter — in or out.
Then print the numerator and denominator, not just the ratio. crates/atlasx could not land on §33's
published 75.4% under any variant it tried — it came out 0.1 point above, about two lines in 1,210 —
so it printed both figures in lib.rs to make the gap checkable rather than arguable. That is the
right response to an irreducible discrepancy.
Write percentages to one decimal place. Two decimals produce a token tools/coverage.sh reads as
a blueprint citation; see the classify-blueprint-modules skill.
Run the sensitivity, not just the measurement
Three knobs. Report what each does, because which one moves is itself the finding.
Threshold is usually inert, and the reason is structural. Sharing in most sections is bimodal: a
line is either in exactly one module or in all of them, with almost nothing between.
crates/worldfactory found §27 gives 53.6% at k=22, k=20 and k=12 alike — 539 distinct lines in
exactly one module, 28 in all twenty-two, six anywhere between. crates/megafactory found §35
identical at k = 50%, 80% and 100%. crates/bioevalx found §26 and §07 identical at 50, 80 and
100%. Five of crates/sweep's six sections do not move by a tenth of a point between t=0.3 and
t=0.9.
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.
- 11d ago First seen · 138 lines · 71 tokens per session scan A 89a8b9a67541
measure-section-boilerplate is a skill published in the GitHub repository AURORA-NEURO/aurora-agent (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 2,102 once invoked, about $0.0004 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-31.
Other skills, from other repositories
halopsa
Every HaloPSA, HaloITSM and HaloCRM feature, plus a local SQLite store and cross-entity views the API can't return. Trigger phrases: triage my Halo queue, check SLA breaches in HaloPSA, who is overloaded in Halo, client card for Acme in Halo, Halo contract burn-down, what changed in Halo since this morning, find time…
veeam
Use when the user asks to check Veeam backup health across customers, find failing or stale backup jobs, surface workloads past their RPO, triage VSPC alarms, or report per-tenant license usage from a Veeam Service Provider Console. Syncs every tenant into a local SQLite mirror so it answers multi-tenant backup…
cipp
First single-binary CLI for CIPP - offline SQLite store, fleet posture analytics, and cross-tenant fan-out no other CIPP tool has. Trigger phrases: check MFA across all my tenants, find unused M365 licenses, offboard users from a CSV in CIPP, which tenants drifted off baseline, list CIPP tenants, use cipp, run…
appdirect
Every documented AppDirect marketplace operation in one binary, plus offline sync and billing-reconciliation joins. Trigger phrases: reconcile appdirect billing, which appdirect payments failed this week, what changed in appdirect subscriptions, show my appdirect pipeline, appdirect company 360, use appdirect, run…
connectwise-manage
Every ConnectWise PSA workflow from the terminal - with a typed conditions query builder, offline SQLite sync, and cross-entity views (unbilled work, account 360, board triage) the PSA web UI can't give you. Trigger phrases: list connectwise tickets, triage the help desk board, find unbilled time in connectwise…
immybot
Every ImmyBot endpoint typed, plus a local SQLite mirror that answers the cross-tenant questions the web UI cannot. Trigger phrases: what failed in last night's maintenance window, which tenants are still on an old version of chrome, why didn't this computer get the deployment, what changed in the fleet since…