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.01204 |
| Opus 5.5 | $0.00030 | $0.00482 |
| Sonnet 5.5 | $0.00015 | $0.00241 |
| Haiku 4.5 | $0.00008 | $0.00120 |
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 20d 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 — 111 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)
Rustdoc doctests can report the same block inline as Couldn't run the test: An Application Control policy has blocked this file. (os error 4551) without Cargo's never executed wording.
Count both forms; tools/status.sh --tests includes both in its blocked-process count.
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 and rustdoc's inline
Application Control diagnostic 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.
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.
- 20d ago Changed · +4 lines fc67e4ac4e0c
- 1mo 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 21d ago), licensed Apache-2.0. It adds 76 tokens to every session and 1,204 once invoked, about $0.0003 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-31.
Other skills, from other repositories
verify-msp-skills
Drive one msp-skills connector (skills/ , any of the 84) the way a user does and prove it with evidence: install.sh, the -cli CLI, and the -mcp server over stdio and over HTTP, in an isolated HOME against a local fake vendor. Use to check a connector's user path before or after a reprint, to compare press versions…
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.
quantum-vqe
A runnable guide to the variational quantum eigensolver (VQE), a quantum algorithm that estimates the lowest energy of a mathematical system by adjusting a parameterized circuit. It uses Pauli Hamiltonians, a specified circuit form, and SciPy optimization.
quantum-vqls
A runnable guide to the variational quantum linear solver (VQLS), a quantum method that estimates a solution to a system of linear equations by optimizing a parameterized circuit. It uses Qiskit and reports the numerical residual and why optimization stopped.
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.
quantum-circuit-verification
A local checker for deciding whether two small OpenQASM 2 quantum circuits perform the same quantum transformation. OpenQASM 2 is a text format for describing quantum circuits.