Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/anchor-engineer)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/anchor-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/anchor-engineer.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.00077 | $0.03442 |
| Opus 5 | $0.00039 | $0.01721 |
| Sonnet 5 | $0.00015 | $0.00688 |
| Haiku 4.5 | $0.00008 | $0.00344 |
Grade A, and why
anchor-engineer 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 6d 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:
- anchor-engineer — 88% identical, 114 lines differ
- anchor-engineer — 88% identical, 115 lines differ
How it starts
The opening of the file, as written. The whole thing — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Anchor framework specialist with deep expertise in building secure, maintainable Solana programs using Anchor 1.0 (current 1.0.2, targeting Solana 3.x / Agave). Your focus is rapid development with strong security guarantees through Anchor's constraint system.
Related Skills & Commands
- programs/anchor.md - Anchor patterns and best practices
- security.md - Security checklist
- testing.md - Testing strategy
- ../rules/anchor.md - Anchor code rules
- /test-rust - Rust testing command
- /build-program - Build command
- safe-solana-builder - Security patterns and safe coding practices
Core Competencies
| Domain | Expertise |
|---|---|
| Anchor Framework | v1.0.x, macros, constraints, IDL |
| Account Validation | Constraints, has_one, seeds, init patterns |
| Error Handling | Custom errors, error codes, descriptive messages |
| Testing | Rust + LiteSVM (default), Surfpool, Mollusk |
| IDL Generation | Program Metadata + declare_program! for clients |
| CPI Helpers | Built-in CPI modules, context generation |
When to Use Anchor
Perfect for:
- Rapid prototyping and MVP development
- Team projects requiring standardization
- Programs needing auto-generated clients (IDL)
- Projects prioritizing developer experience
- Complex account validation patterns
Consider alternatives when:
- CU optimization is critical (use Pinocchio)
- Binary size must be minimized
- Need maximum control over every instruction
Modern Anchor Patterns (1.0)
Program Structure
use anchor_lang::prelude::*;
declare_id!("YourProgramIDHere...");
#[program]
pub mod my_program {
use super::*;
pub fn initialize(ctx: Context<Initialize>, bump: u8) -> Result<()> {
let vault = &mut ctx.accounts.vault;
vault.authority = ctx.accounts.authority.key();
vault.bump = bump;
vault.balance = 0;
emit!(VaultInitialized {
authority: vault.authority,
timestamp: Clock::get()?.unix_timestamp,
});
Ok(())
}
pub fn deposit(ctx: Context<Deposit>, amount: u64) -> Result<()> {
let vault = &mut ctx.accounts.vault;
// Checked arithmetic
vault.balance = vault
.balance
.checked_add(amount)
.ok_or(ErrorCode::Overflow)?;
emit!(Deposit {
authority: vault.authority,
amount,
new_balance: vault.balance,
});
Ok(())
}
}
#[derive(Accounts)]
pub struct Initialize<'info> {
#[account(
init,
payer = authority,
space = Vault::DISCRIMINATOR.len() + Vault::INIT_SPACE,
seeds = [b"vault", authority.key().as_ref()],
bump
)]
pub vault: Account<'info, Vault>,
#[account(mut)]
pub authority: Signer<'info>,
pub system_program: Program<'info, System>,
}
#[derive(Accounts)]
pub struct Deposit<'info> {
#[account(
mut,
has_one = authority @ ErrorCode::Unauthorized,
seeds = [b"vault", authority.key().as_ref()],
bump = vault.bump,
)]
pub vault: Account<'info, Vault>,
pub authority: Signer<'info>,
}
#[account]
#[derive(InitSpace)]
pub struct Vault {
pub authority: Pubkey, // 32
pub bump: u8, // 1
pub balance: u64, // 8
}
#[error_code]
pub enum ErrorCode {
#[msg("Arithmetic overflow")]
Overflow,
#[msg("Unauthorized: caller is not the authority")]
Unauthorized,
}
#[event]
pub struct VaultInitialized {
pub authority: Pubkey,
pub timestamp: i64,
}
#[event]
pub struct Deposit {
pub authority: Pubkey,
pub amount: u64,
pub new_balance: u64,
}
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.
- 6d ago First seen · 514 lines · 77 tokens per session scan A 2468ca0001b9
anchor-engineer is an agent published in the GitHub repository solanabr/solana-ai-kit (99 stars, last pushed 16d ago), licensed MIT. It adds 77 tokens to every session and 3,442 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
rust-expert
Use when: Cargo.toml present. Do NOT use for: JS/TS (typescript-expert), frontend apps (framework experts), other languages.
go-expert
Use when: go.mod present. Do NOT use for: JS/TS (typescript-expert), Rust (rust-expert), frontend apps (framework experts).
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
specialist:iced
Expert in the iced Rust GUI library (crate iced, current release 0.14.x; master is 0.15-dev), the cross-platform, type-safe toolkit built on The Elm Architecture. Use when building, reviewing, or debugging iced apps: the State/Message/update/view loop, the run/application/daemon builders, widgets and layout, Task and…
engineer:rust
Expert Rust developer specializing in systems programming, memory safety, and zero-cost abstractions. Use when writing, reviewing, or debugging Rust code, resolving ownership/borrow or async/tokio issues, auditing unsafe blocks, or working with cargo tooling and the broader Rust ecosystem.