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/verify-crate/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/verify-crate)<a href="https://agentmods.dev/skills/aurora-neuro/aurora-agent/verify-crate"><img src="https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/verify-crate/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/verify-crate"><img src="https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/verify-crate.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.00076 | $0.01134 |
| Opus 5 | $0.00038 | $0.00567 |
| Sonnet 5 | $0.00015 | $0.00227 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
verify-crate 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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify a crate
Green means both of these, per crate:
cargo test -p bioprism-<crate> --offline
cargo clippy -p bioprism-<crate> --all-targets --offline
Zero failures, zero warnings. --offline is not optional — this workspace builds against pinned
versions with no network, and omitting it produces a confusing registry error rather than a build.
Do not trust a reported test count without running it
Agents and humans both miscount. Run the suite yourself and sum the test result lines:
cargo test -p bioprism-<crate> --offline 2>&1 | grep -E "^test result: ok" | awk '{s+=$4} END {print s}'
The failure that is not a failure
Windows Application Control sometimes blocks a freshly linked test binary:
error: test failed, to rerun pass `-p bioprism-<crate> --test <suite>`
Caused by:
could not execute process ... (never executed)
Caused by:
An Application Control policy has blocked this file. (os error 4551)
A suite that never ran looks exactly like a suite that failed. Worse, cargo test continues to
the next binary, so a naive sum silently under-reports — this has already produced a wrong count
once (27 reported where the true figure was 75).
Force a relink to get a new binary hash the policy allows:
touch crates/<crate>/tests/*.rs
cargo test -p bioprism-<crate> --offline
If a per-crate count looks lower than expected, check for never executed before concluding
anything about the code.
It bites the workspace sum harder than any single crate
This is the part that keeps costing time. A blocked binary makes cargo test --workspace lose
every test after it, silently — the run reports error: test failed, cargo moves on, and the sum
you take at the end is short by an amount nothing on screen tells you.
It has now hit five recorded times in this repository:
| Where | Reported | True |
|---|---|---|
workspace, Batch I (3a5bae2) |
344 | 4,327 |
workspace, fiber batch (0f5b53b) — three binaries blocked |
short by 66 | 6,171 |
crates/fabric (18c5475) |
130 | 176 |
crates/bioevalx (9a04c8b) — one blocked, three later never ran |
— | 113 |
| the original per-crate case in this skill | 27 | 75 |
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.
- 9d ago First seen · 107 lines · 76 tokens per session scan A ee7108027e31
verify-crate is a skill published in the GitHub repository AURORA-NEURO/aurora-agent (1 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 1,134 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
klever-dev
End-to-end Klever blockchain development — smart contracts (Rust/WASM), transaction building (@klever/connect, klever-go-sdk), deployment via ksc + koperator, and on-chain interaction via MCP tools. Use when the task involves KLV, KDA tokens, klv1 addresses, Klever smart contracts, or Klever node/API interaction.
qa
QA test a live website with Axon discovery/content evidence plus browser automation when interaction is required. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.
rust-development
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
cargo-fuzz
Use when initializing, running, measuring coverage, or triaging a cargo-fuzz target in a Rust crate. Not for remote, credential, publish, deploy, or irreversible changes.
testing-python
Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, async testing, and CI integration.
rust-sota-arsenal
Reference guide for state-of-the-art Rust tooling across refactoring, profiling, benchmarking, testing, and SIMD optimization. Use whenever the.