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.
git clone --depth 1 https://github.com/kenny-stacks/stacks-claude-pluginWrote 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/commands/kenny-stacks/stacks-claude-plugin/expert-advice)<a href="https://agentmods.dev/commands/kenny-stacks/stacks-claude-plugin/expert-advice"><img src="https://agentmods.dev/badge/commands/kenny-stacks/stacks-claude-plugin/expert-advice.svg" alt="Measured on agentmods" 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.00000 | $0.00772 |
| Opus 5 | $0.00000 | $0.00386 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
expert-advice 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 8d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/stacks:expert-advice
Get expert-level review and advice for your Clarity smart contracts.
What This Does
This command performs a comprehensive review of your Clarity contracts against best practices, security patterns, and common pitfalls. It provides actionable recommendations for improvement.
Instructions
Step 1: Explore Contracts
Find all Clarity contracts in the project:
find . -name "*.clar" -type f | grep -v node_modules
Read each contract file to understand the codebase.
Step 2: Fetch Latest Documentation
Fetch the latest Stacks documentation for reference:
https://docs.stacks.co/llms.txt
Use this to ensure advice aligns with current best practices and API versions.
Step 3: Review Against Best Practices
Analyze each contract for:
Coding Style (Clarity Book Ch13)
- No unnecessary
beginblocks - Sequential
asserts!instead of nestedif - Explicit error codes (no
unwrap-panic) - Meaningful error constants (HTTP-style + domain-specific)
- Single
letblocks where applicable
Security Patterns
- Authorization checks on sensitive functions
- Input validation (bounds checking, type validation)
- Proper use of
asserts!vsunwrap!vstry! - Post-conditions for STX/token transfers in frontend
- No reentrancy vulnerabilities
- Safe arithmetic (overflow/underflow considerations)
Storage Optimization
- Minimal on-chain storage
- Hash storage for large data
- No redundant computed fields
- Efficient map usage
Upgradability (if applicable)
- Dynamic principals for upgradable references
- Data/logic separation
- Clear governance patterns
Step 4: Generate Report
Present findings in this format:
## Contract Review: {contract-name}
### Summary
[Brief overview of what the contract does]
### Strengths
- [Good patterns observed]
### Issues Found
#### Critical (Security)
- [Issue description]
- Location: `contracts/name.clar:line`
- Fix: [Suggested fix with code]
#### High (Best Practices)
- [Issue description]
- Location: `contracts/name.clar:line`
- Fix: [Suggested fix]
#### Medium (Optimization)
- [Issue description]
#### Low (Style)
- [Issue description]
### Recommendations
1. [Prioritized action items]
### References
- [Relevant documentation links]
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.
- 8d ago First seen · 124 lines · 0 tokens per session scan A fd2f41e4cafd
expert-advice is a command published in the GitHub repository kenny-stacks/stacks-claude-plugin (11 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 772 tokens. 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 commands, from other repositories
deploy
Deploy Solana program (devnet first, then mainnet).
invariant
Generate Foundry invariant tests for property-based fuzzing. The high-value command for serious teams.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.
docs-remove
Remove a user-defined source alias from sources.yaml, optionally deleting its cached Markdown.
analyze
Conduct a full gas optimization analysis on a Foundry Solidity project.
checklist
Generate a custom checklist for the current feature based on user requirements.