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 saski/arnesto --skill lustragit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/lustra)<a href="https://agentmods.dev/skills/saski/arnesto/lustra"><img src="https://agentmods.dev/badge/skills/saski/arnesto/lustra/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/saski/arnesto/lustra"><img src="https://agentmods.dev/badge/skills/saski/arnesto/lustra.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.00258 | $0.01439 |
| Opus 5.5 | $0.00103 | $0.00576 |
| Sonnet 5.5 | $0.00052 | $0.00288 |
| Haiku 4.5 | $0.00026 | $0.00144 |
Grade A, and why
lustra 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lustra
Lustra wraps real code-hygiene tooling and applies judgment on top of it. It does not guess where a tool would. It runs the tool, filters false positives, ranks what matters, and applies only the changes the user approves.
Dispatch
$1 is the command. $2 and beyond are the target (a path or glob). When no target is
given, default to the whole repository.
- If
$1is empty orhelp, print the command list below and stop. - Otherwise read
${CLAUDE_SKILL_DIR}/reference/$1.mdand follow it exactly, scoped to the target. Ifreference/$1.mddoes not exist, say so and print the command list.
Commands
Grouped by lifecycle phase. audit runs the diagnostic ones together.
Assess / start
audit— meta-command: one graded health report across every dimension (due diligence).baseline— scaffold the guardrail configs a project should have, for the detected stack.
Iterate
review— structured correctness / design / slop review of a diff or path.types— type-checker triage; catchany/@ts-ignore-style evasion.tests— run the suite, coverage on the diff, catch fake/empty tests.analyze— the linter's findings plus AI-slop smells that no rule catches.format— formatting drift, fixed mechanically.
Polish
security— vulnerabilities: secrets, injection, broken authorization, vulnerable deps.license— dependency license compatibility and IP risk.deadcode— unused files, exports, and dependencies; deletes only what is confirmed.deps— dependency health and upgrades: outdated, deprecated, duplicated. Reports unused deps and advisories but defers deletion todeadcodeand vuln fixes tosecurity.design— module/package design quality: SOLID, or cohesion/coupling/composition for non-OO stacks. Module-scoped, unlike diff-scopedreviewor layout-scopedstructure.observability— logging and instrumentation quality so failures are diagnosable.perf— performance smells: N+1, blocking IO, unbounded growth, bundle weight.docs— documentation drift and undocumented public surface.
What ships with it
18 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.
- reference/analyze.md 1.9 KB
- reference/audit.md 2.0 KB
- reference/baseline.md 1.6 KB
- reference/ci.md 1.7 KB
- reference/deadcode.md 1.6 KB
- reference/deps.md 2.2 KB
- reference/design.md 1.7 KB
- reference/docs.md 1.4 KB
- reference/format.md 1.5 KB
- reference/license.md 2.1 KB
- reference/migrate.md 1.6 KB
- reference/observability.md 1.7 KB
- reference/perf.md 1.7 KB
- reference/review.md 1.6 KB
- reference/security.md 1.8 KB
- reference/structure.md 1.5 KB
- reference/tests.md 1.5 KB
- reference/types.md 1.3 KB
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 · 99 lines · 258 tokens per session scan A 74f6e187528f
lustra is a skill published in the GitHub repository saski/arnesto (6 stars, last pushed 7d ago), licensed Unlicense. It adds 258 tokens to every session and 1,439 once invoked, about $0.0010 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-09-03.
Other skills, from other repositories
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
compute-sanitizer-diagnose-cuda-bugs
Detect and diagnose CUDA correctness bugs with NVIDIA Compute Sanitizer. Routes GPU memory errors, shared-memory data races, uninitialized-memory reads, and synchronization/barrier bugs to the right sub-tool (memcheck, racecheck, initcheck, synccheck) and explains how to build, run, and read the report. Use when…
doca-debug
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca symbol, a runtime call returning DOCAERROR, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime →…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
doca-dpa-hl-tracer
Use this skill when the user runs docadpahltracer to capture/decode DPA-side traces at the programming-events layer (kernel entry/exit, sync points, comm primitive calls, RDMA WR submission, completion drain) — picking TRACE vs CRIT, tuning the JSON config (file-size limits + filesizelimitpolicy, thread…