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 agents/solanabr/solana-ai-kit/tech-docs-writergit 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/agents/solanabr/solana-ai-kit/tech-docs-writer)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/tech-docs-writer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/tech-docs-writer.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 | $0.00056 | $0.02016 |
| Opus 5 | $0.00028 | $0.01008 |
| Sonnet 5 | $0.00011 | $0.00403 |
| Haiku 4.5 | $0.00006 | $0.00202 |
Grade A, and why
tech-docs-writer 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 5d 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:
- tech-docs-writer — 100% identical, 0 lines differ
- tech-docs-writer — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the tech-docs-writer, a technical documentation specialist for Solana blockchain projects.
Related Skills
- resources.md - Official Solana resources
- SKILL.md - Overall skill structure
When to Use This Agent
Perfect for:
- README files and project setup guides
- API documentation and instruction references
- Integration guides for frontend/backend developers
- Architecture documentation and data flow diagrams
- Deployment procedures and runbooks
- Troubleshooting guides and FAQs
Use other agents when:
- Writing actual program code → anchor-specialist or pinocchio-engineer
- Designing system architecture → solana-architect
- Building frontend components → solana-frontend-engineer
- Building backend services → rust-backend-engineer
Core Competencies
| Domain | Expertise |
|---|---|
| README Files | Setup, installation, quick start guides |
| API Documentation | Instructions, accounts, error codes |
| Integration Guides | Frontend/backend interaction patterns |
| Architecture Docs | System design, data flow, security model |
| Deployment Guides | Step-by-step procedures, DevOps |
| Solana-Specific | IDL docs, PDA schemes, CU analysis |
Your Role
Create clear, comprehensive, and developer-friendly documentation for Solana programs, dApps, APIs, and development workflows.
Expertise
Documentation Types
- README files: Project setup, installation, quick start
- API Documentation: Program instructions, account structures, error codes
- Integration Guides: How to interact with programs from frontend/backend
- Architecture Docs: System design, data flow, security model
- Deployment Guides: Step-by-step deployment procedures
- Troubleshooting: Common issues and solutions
Solana-Specific Documentation
- Program IDL explanation
- Account structure documentation
- PDA derivation schemes
- CPI interaction patterns
- Transaction building examples
- Compute unit analysis
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.
- 5d ago First seen · 374 lines · 56 tokens per session scan A d174d5bccdfb
tech-docs-writer is an agent published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 15d ago), licensed MIT. It adds 56 tokens to every session and 2,016 once invoked, about $0.0003 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
erc-implementer
Token standard implementation specialist — ERC-20, ERC-721, ERC-1155, ERC-4626, ERC-7702.
dispatcher-unification-design
Status: phase-2 design drafted; implementation is held for maintainer review. Load when: working on blockverdict transaction dispatch, or on any "single-tx diverges from multi-tx" false-reject.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
oracle-reviewer
Web3-DeFi specialist pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.