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 agentmods add skills/cdsecurity/cdsecurity-skills/rust-audit-prepnpx skills add CDSecurity/cdsecurity-skills --skill rust-audit-prepgit clone --depth 1 https://github.com/CDSecurity/cdsecurity-skillsWhat 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 | $0.00181 | $0.03145 |
| Opus 5 | $0.00090 | $0.01572 |
| Sonnet 5 | $0.00036 | $0.00629 |
| Haiku 4.5 | $0.00018 | $0.00314 |
Grade A, and why
rust-audit-prep 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solana / Rust Audit Preparation
You are a Solana audit preparation assistant. Your job is to systematically scan a project across 5 phases, score each one, and print a compact terminal report.
The goal: surface everything a team can fix themselves — test gaps, missing docs, stale TODOs, outdated dependencies, compute waste, unsafe patterns — so paid auditors focus on complex protocol-level issues.
Supports both Anchor-based and native solana_program Rust programs.
Modes
- Default: full pipeline, all 5 phases, terminal output.
coverage|docs|hygiene|deps|practices|scan: run only that phase.--fix: auto-apply fixes where possible (doc stubs,println!removal,overflow-checksaddition).--report <path>: additionally write a detailed markdown report to file (readsreferences/report-template.md).
Report Format
Clean markdown. Each phase = one titled section with a results table.
Score summary at the end. No deduction numbers, no weights, no [-N] annotations.
The report should read like a professional checklist a dev team can hand to their lead.
The report has these sections in order:
- Header (project name, framework, scope)
- Phase 1–5, each as a titled section with a results table
- Score Summary table
- Quick Wins table
Phase section template
## 1. Test Coverage
| Status | Finding | Recommendation |
|--------|---------|----------------|
| FAIL | No test files shipped in repo — README confirms tests are external | Publish integration tests for auditor reproducibility |
| PASS | Inline unit tests in core module | — |
| PASS | Prior audit history — extensive testing implied | — |
- Status:
PASSorFAIL - Finding: concise description of what was checked and the result
- Recommendation: specific action to fix (only for FAIL rows; use
—for PASS) - Group related PASS items into single rows where natural
Score Summary
## Score Summary
| Phase | Score |
|-------|-------|
| 1. Test Coverage | 60/100 |
| 2. Documentation | 72/100 |
| 3. Code Hygiene | 72/100 |
| 4. Dependencies | 90/100 |
| 5. Best Practices | 88/100 |
| **Overall** | **78/100 — Almost Ready** |
What ships with it
8 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 First seen · 299 lines · 181 tokens per session scan A c21a8e8c51f0
rust-audit-prep is a skill published in the GitHub repository CDSecurity/cdsecurity-skills (51 stars, last pushed 4mo ago), licensed MIT. It adds 181 tokens to every session and 3,145 once invoked, about $0.0009 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-30.
Other skills, from other repositories
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
ansem-crypto
Use when evaluating crypto narratives, attention rotation, memecoin cycles, Solana-style ecosystem momentum, social distribution, and reflexive retail flows in an Ansem-style crypto market framework.
copy-trading-solana
Copy trade Solana wallets - mirror trades automatically.
[REPLACE: SKILL_NAME]
Price and volume tracker for [REPLACE: TOKENSYMBOL] with anomaly alerts above [REPLACE: ALERTTHRESHOLDPCT]% movement.
kraken-order-types
Complete reference for all spot and futures order types and modifiers.
crypto-market-rank
Crypto market rankings and leaderboards. Query trending tokens, top searched tokens, Binance Alpha tokens, tokenized stocks, social hype sentiment ranks, smart money inflow token rankings, top meme token rankings from Pulse launchpad, and top trader PnL leaderboards. Use this skill when users ask about token rankings…