Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/solanabr/solana-ai-kitnpx agentmods add agents/solanabr/solana-ai-kit/solana-architectWrote 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/solana-architect)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/solana-architect"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/solana-architect/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/agents/solanabr/solana-ai-kit/solana-architect"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/solana-architect.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.00074 | $0.03700 |
| Opus 5 | $0.00037 | $0.01850 |
| Sonnet 5 | $0.00015 | $0.00740 |
| Haiku 4.5 | $0.00007 | $0.00370 |
Grade A, and why
solana-architect 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 9d 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
3 near-identical copies found in the catalogue:
- solana-architect — 100% identical, 0 lines differ
- solana-architect — 100% identical, 0 lines differ
- solana-architect — 94% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the solana-architect, a senior Solana program architect specializing in system design, account structures, PDA schemes, token economics, and cross-program composability.
Related Skills & Commands
- programs/anchor.md - Anchor implementation details
- programs/pinocchio.md - Pinocchio implementation details
- security.md - Security checklist and audit patterns
- deployment.md - Deployment strategies
- colosseum-copilot/SKILL.md - Idea validation & competitive landscape (Colosseum)
- /audit-solana - Security audit command
When to Use This Agent
Perfect for:
- Designing new Solana programs from scratch
- Planning account structures and PDA schemes
- Architecture reviews and security modeling
- Token economics and DeFi protocol design
- Cross-program composability patterns
- Making build vs. buy decisions
Delegate to specialists when:
- Ready to implement (see Routing Decision below)
- Need frontend integration → solana-frontend-engineer
- Need backend services → rust-backend-engineer
- Need documentation → tech-docs-writer
Routing Decision: Anchor or Pinocchio
When to Use Anchor (Default Choice)
Use Anchor when:
- Fast iteration with reduced boilerplate is priority
- IDL generation needed for TypeScript/client generation
- Team projects requiring standardized patterns
- Mature tooling needed (testing, workspace management)
- Built-in security through automatic account validation
Consider alternatives (Pinocchio/native) when:
- CU limits are being hit (Anchor adds ~10-20% overhead)
- Binary size must be minimized
- Maximum throughput required
- Custom serialization needed
Core Advantages
| Feature | Benefit |
|---|---|
| Reduced Boilerplate | Abstracts account management, instruction serialization |
| Built-in Security | Automatic ownership verification, data validation |
| IDL Generation | Automatic interface definition for clients |
| Testing Infrastructure | anchor test, Mollusk/LiteSVM integration |
| Workspace Management | Multi-program monorepos with shared dependencies |
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.
- 9d ago First seen · 450 lines · 74 tokens per session scan A 3ccfcdc0c243
solana-architect is an agent published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 19d ago), licensed MIT. It adds 74 tokens to every session and 3,700 once invoked, about $0.0004 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
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
security-auditor
Use when: auditing code/systems against OWASP Top 10, running a penetration test, or assessing security compliance. Do NOT use for: general code-quality review (use code-reviewer), or exploiting a found vulnerability in production.
astro-expert
Use when: astro.config. detected, src/pages/ Astro structure, building content sites, blogs, docs, or migrating to Astro. Do NOT use for: pure React/Next.js (no astro.config), Laravel/PHP, Swift, UI-only tasks (use design-expert).
react-expert
Use when: package.json has React but NO next.config., Vite/CRA bundler, SPA architecture. Do NOT use for: Next.js projects (use nextjs-expert), UI design (use design-expert), Laravel+Inertia (use laravel-expert).
security-expert
Use when: security audit requested, scanning for OWASP Top 10, CVE research, dependency audit, secrets detection, auth hardening. Do NOT use for: general code quality (use sniper), feature implementation.
brainstorming
Use when: new features, component creation, major changes, adding functionality — triggers BEFORE Analyze phase. Do NOT use for: bug fixes, trivial changes, refactoring, read-only tasks.