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 OutlineDriven/outline-driven-development --skill chain-vulnerability-scannergit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/chain-vulnerability-scanner)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/chain-vulnerability-scanner"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/chain-vulnerability-scanner.svg" alt="Measured on agentmods" 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.00047 | $0.03209 |
| Opus 5 | $0.00023 | $0.01605 |
| Sonnet 5 | $0.00009 | $0.00642 |
| Haiku 4.5 | $0.00005 | $0.00321 |
Grade A, and why
chain-vulnerability-scanner 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chain vulnerability scanner
A single read-only scan operation that classifies a blockchain codebase by ecosystem, loads only that ecosystem's detector catalog, and emits severity-ranked findings tied to reachable code paths. Six ecosystems are supported; each owns one flat reference file under references/ that holds its detectors, applicability gates, tool requirements, severity distinctions, and ecosystem caveats. This file holds the shared routing, authority, procedure, cross-cutting rules, failure behavior, and output contract.
Ecosystem routing
| Ecosystem | Source indicators | Reference file |
|---|---|---|
| Algorand | .teal files; .py importing PyTeal or Algorand SDK (from pyteal import *, from algosdk import *, Txn, Gtxn, Global, InnerTxnBuilder, OnComplete, @router.method, @Subroutine); approval_program.py/clear_program.py, contract.teal/signature.teal, Beaker references. |
references/algorand.md |
| Cairo / Starknet | .cairo files; Scarb.toml; contract markers #[contract], #[storage], #[external(v0)], #[l1_handler], #[constructor], felt252, ContractAddress, get_caller_address(), send_message_to_l1_syscall. Optional L1 bridge Solidity contracts for cross-layer patterns. |
references/cairo.md |
| Cosmos SDK | Go source with Cosmos SDK x/ modules and go.mod; ibc-go; Ethermint/EVM precompiles (evmutil/feemarket); Rust contracts using cosmwasm_std. |
references/cosmos-sdk.md |
| Solana | Solana or Anchor Rust (.rs) program files. |
references/solana.md |
| Substrate | Substrate FRAME pallet Rust source tree or file within a runtime. | references/substrate.md |
| TON | FunC or Tact source (function definitions, message handlers, recv_internal, recv_external, op:: constants, @interface annotations). |
references/ton.md |
If the codebase matches none of the indicators above, stop and report that no supported chain surface applies. Do not run any catalog. Route generic non-chain security review to security-review instead: chain-vulnerability-scanner loads ecosystem-specific detector catalogs for six supported blockchain ecosystems; security-review runs STRIDE and OWASP on any codebase. The split is: supported chain ecosystem → chain-vulnerability-scanner; any other codebase → security-review.
What ships with it
7 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.
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.
- 2d ago Changed · -14 tokens per session 34b4b0ce82fa
- 4d ago First seen · 118 lines · 61 tokens per session scan A a556dc3176d9
chain-vulnerability-scanner is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 3,209 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
smart-contract-code-maturity-assessor
Use when a smart-contract codebase needs an evidence-based maturity scorecard and prioritized improvement roadmap. Rates nine categories from code and explicit off-chain evidence, computes an aggregate score, and produces a CRITICAL-to-MEDIUM roadmap. Not for vulnerability auditing, source fixes, or claims about…
smart-contract-guidelines-advisor
Use when a smart-contract project needs architecture, implementation, dependency, or testing guidance. Produces an evidence-backed assessment with recommendations. Not for maturity — use smart-contract-code-maturity-assessor; not for audit prep — use smart-contract-audit-prep.
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
api-design
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
nansen-exit-signals
Is smart money exiting a token I hold? Net flow direction, seller breakdown by label, and recent SM trades.
solidity
Expert in Solidity smart contract development with security and gas optimization.