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/solanabr/solana-ai-kitWrote 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/solanabr/solana-ai-kit/write-docs)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/write-docs"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/write-docs/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/commands/solanabr/solana-ai-kit/write-docs"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/write-docs.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00311 |
| Opus 5.5 | $0.00007 | $0.00124 |
| Sonnet 5.5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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 25d 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, 82 lines differ
- write-docs — 95% identical, 82 lines differ
What it actually says
Document the code in $ARGUMENTS. Take facts from the source and the IDL (target/idl/<name>.json) rather than from memory. For a full documentation set (guides, architecture, runbooks), hand off to the tech-docs-writer agent.
What each doc type needs
| Type | Include |
|---|---|
| Program | Program IDs per cluster. Per instruction: accounts (signer, writable, PDA seeds), arguments with valid ranges, errors with codes, who may call it, CU estimate. Per account: fields with sizes, total size including the discriminator, rent, and which instructions create, mutate and close it |
| SDK/API | Functions with parameters, return values, thrown errors, and a working example |
| Unity/C# component | Serialized fields, events, usage; patterns in solana-game SKILL.md |
| README | What it is, program IDs, install, quick start, instruction summary, test and deploy commands, audit status |
Rules
- Examples must run against the current IDL and generated client; mark any you could not run.
- State the security assumptions: who can call what, which accounts must be trusted, what the upgrade authority can change.
- Explain why a non-obvious choice was made; skip what the code already says plainly.
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.
- 25d ago Changed · -56 lines · +6 tokens per session 8312b3996a44
- 26d ago Changed f2e7da20951c
- 1mo 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 (104 stars, last pushed 26d ago), licensed MIT. It adds 17 tokens to every session and 311 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
explain-architecture
Analyze and explain software architecture with ASCII diagrams and pattern detection. Creates visual representations of system design.
prompt
Create or optimize prompts using best practices.
amend
Amend last commit safely. Use for amend, fix last commit, update commit, modify commit.
test
Test commit. Use for add tests, update tests, test coverage, unit test, spec.
db-migrate
You are a database migration expert specializing in zero-downtime deployments, data integrity, and multi-database environments. Create comprehensive migration scripts with rollback strategies, validation checks, and performance optimization.