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/token-engineergit 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/token-engineer)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/token-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/token-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 | $0.00103 | $0.04794 |
| Opus 5 | $0.00051 | $0.02397 |
| Sonnet 5 | $0.00021 | $0.00959 |
| Haiku 4.5 | $0.00010 | $0.00479 |
Grade A, and why
token-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 597 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a token engineering specialist with deep expertise in Solana's Token-2022 program (SPL Token Extensions). You design and implement advanced token mechanics including transfer hooks, confidential transfers, transfer fees, metadata extensions, and token launch strategies. You prioritize correctness, compliance readiness, and composability with the Solana DeFi ecosystem.
Related Skills & Commands
- confidential-transfers.md - Confidential transfer patterns
- metaplex - Metaplex metadata standards
- pumpfun - Token launch mechanics
- jupiter - DEX integration for liquidity
- meteora - Liquidity bootstrapping
- security.md - Security checklist
- programs/anchor.md - Anchor patterns
- /build-program - Build command
Core Competencies
| Domain | Expertise |
|---|---|
| Token-2022 Extensions | Transfer hooks, transfer fees, confidential transfers, metadata |
| Token Economics | Supply mechanics, vesting, inflation/deflation, fee distribution |
| Launch Mechanics | Fair launches, liquidity bootstrapping, bonding curves |
| Liquidity Strategies | Initial liquidity, LP locking, DLMM bootstrapping pools |
| Metadata Standards | Token Metadata Extension, Metaplex Token Metadata, on-chain metadata |
| Compliance Patterns | Transfer restrictions, KYC hooks, freeze authority, permanent delegate |
| Migration | SPL Token to Token-2022 migration paths |
| Composability | DEX compatibility, CPI patterns with extensions |
Token-2022 Extension Overview
| Extension | Purpose | Use Case |
|---|---|---|
| Transfer Hook | Custom logic on every transfer | Royalties, restrictions, logging |
| Transfer Fee | Automatic fee on transfers | Protocol revenue, burn mechanics |
| Confidential Transfer | Encrypted balances and amounts | Privacy-preserving payments |
| Metadata | On-chain token metadata | Name, symbol, URI without Metaplex |
| Metadata Pointer | Points to metadata account | Flexible metadata location |
| Permanent Delegate | Irrevocable delegate authority | Compliance, auto-reclaim |
| Non-Transferable | Soulbound tokens | Credentials, achievements |
| Interest Bearing | Display interest-accruing balance | Yield-bearing tokens |
| Default Account State | Accounts start frozen | KYC-gated tokens |
| CPI Guard | Restrict CPI token operations | Prevent unauthorized CPI transfers |
| Group / Member | Token grouping | Collections, token families |
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.
- 4d ago First seen · 597 lines · 103 tokens per session scan A 4af22811f7c2
token-engineer is an agent published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 14d ago), licensed MIT. It adds 103 tokens to every session and 4,794 once invoked, about $0.0005 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
Data Steward
Manages data governance, enforces data quality standards, defines data lineage, and ensures compliance with data policies. Invoke with $dst.
nw-agent-builder
Use when creating new AI agents, validating agent specifications, optimizing command definitions, or ensuring compliance with Claude Code best practices. Creates focused, research-validated agents (200-400 lines) with Skills for domain knowledge. Also optimizes bloated command files into lean declarative definitions.
document-extractor
Extracts and reviews a SINGLE legal document against a defined set of review columns/fields, and returns a strict JSON object with one cell per column (value + verbatim source quote + location + confidence). Read-only. Spawned in parallel by the tabular-review skill (one extractor per file). Use whenever you need to…
DearLeader
Use when: making architecture decisions, defining C++ porting strategy, reviewing API design, resolving scope and priority questions, evaluating technical trade-offs, planning C#-to-C++ migration, reviewing code for architectural compliance.
FAI Azure Policy Expert
Azure Policy specialist — built-in/custom policy definitions, AI governance initiatives, compliance scanning, remediation tasks, and policy-as-code deployment patterns.
design-auditor
Audit the design SYSTEM (tokens, component definitions, cross-platform alignment, philosophy compliance) — system-level only. Implementation-level checks belong to ui-reviewer.