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 commands/solanabr/solana-ai-kit/write-docsgit clone --depth 1 https://github.com/solanabr/solana-ai-kitWhat 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.00011 | $0.00500 |
| Opus 5 | $0.00005 | $0.00250 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
write-docs 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- write-docs — 95% identical, 2 lines differ
- write-docs — 95% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate comprehensive documentation for Solana blockchain code.
Code to Document
$ARGUMENTS
Related Context
- Solana Programs: See programs/anchor.md for IDL patterns
- Unity/C#: See solana-game SKILL.md for Unity/C# patterns
- Detailed Templates: See tech-docs-writer agent for full templates
Documentation Strategy
1. Identify Documentation Type
| Type | What to Generate |
|---|---|
| Program | Instructions, accounts, PDAs, errors, security, CU |
| SDK/API | Functions, params, returns, errors, examples |
| Component | Props/properties, events, usage patterns |
| README | Overview, setup, quick start, deployment |
2. Documentation Requirements
For Instructions/Endpoints:
- Accounts table (name, type, description)
- Arguments table (name, type, validation)
- Error codes with descriptions
- Access control notes
- Compute units estimate
- Working code example
For Account Structures:
- Purpose and lifecycle
- Size calculation (include discriminator)
- Field table with types and offsets
- PDA seeds (if applicable)
- Rent cost
For README:
- Program IDs (mainnet/devnet)
- Installation command
- Quick start example
- Instruction summary table
- Security/audit status
3. Best Practices
Do:
- Document ALL public functions/instructions
- Include working code examples
- Explain "why", not just "what"
- Include error scenarios
- Update docs when code changes
Don't:
- Document obvious code
- Leave non-compiling examples
- Skip security considerations
- Forget to document errors
Output
Generate documentation appropriate to the code type:
- Programs: Instruction docs, account docs, error codes
- SDKs: Function docs, type definitions, examples
- Components: Props, events, usage patterns
- Projects: README with setup and deployment
For complex projects, delegate to tech-docs-writer agent.
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 · 77 lines · 11 tokens per session scan A ca338813e5af
write-docs is a command published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 12d ago), licensed MIT. It adds 11 tokens to every session and 500 once invoked, about $0.0001 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 commands, from other repositories
create-hook
Create hooks with brainstorming and security-first design.
validate-hook
Validate hooks for security, performance, and SDK compliance.
evaluate-skill
Manually evaluate a recent skill execution to record qualitative feedback.
setup
The setup command initializes a new Dash node with the specified configuration preset.
nip
Fetch a NIP specification and orient an implementation in Nostrord.
brainblast-deploy-plan
Deployment Intelligence for Anchor programs. Run before anchor deploy so you know how much SOL you need and the exact ordered transaction sequence — instead of working it out by hand.