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/generate-idl-client)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/generate-idl-client"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/generate-idl-client/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/generate-idl-client"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/generate-idl-client.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.00015 | $0.02178 |
| Opus 5 | $0.00008 | $0.01089 |
| Sonnet 5 | $0.00003 | $0.00436 |
| Haiku 4.5 | $0.00002 | $0.00218 |
Grade A, and why
generate-idl-client 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
2 near-identical copies found in the catalogue:
- generate-idl-client — 100% identical, 0 lines differ
- generate-idl-client — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are generating a TypeScript client from a Solana program's IDL. Detect the IDL source and generator, run the appropriate pipeline, and verify the output compiles.
Related Skills
- ext/solana-dev/skill/references/idl-codegen.md - Codama/Shank client generation patterns
- ext/solana-dev/skill/references/programs/anchor.md - Anchor IDL format
Step 1: Detect IDL Source
echo "Detecting IDL source..."
echo ""
# Check for Anchor IDL
if ls target/idl/*.json 2>/dev/null; then
echo "Found Anchor IDL(s) in target/idl/"
IDL_SOURCE="anchor"
ls -la target/idl/*.json
fi
# Check Anchor.toml for program names
if [ -f "Anchor.toml" ]; then
echo ""
echo "Anchor.toml programs:"
grep -A 10 '\[programs' Anchor.toml
fi
# Check for Shank-annotated programs
if grep -r "ShankInstruction\|ShankAccount\|shank" --include="*.rs" programs/ src/ 2>/dev/null | head -5; then
echo ""
echo "Shank annotations detected"
IDL_SOURCE="${IDL_SOURCE:-shank}"
fi
# Check for Codama config
if [ -f "codama.json" ] || [ -f "codama.config.ts" ] || [ -f "codama.config.js" ]; then
echo ""
echo "Codama config found"
IDL_SOURCE="${IDL_SOURCE:-codama}"
fi
# Check for existing IDL files in other locations
if ls idl/*.json 2>/dev/null || ls *.idl.json 2>/dev/null; then
echo ""
echo "Found IDL files in project root or idl/ directory"
fi
echo ""
echo "IDL source: ${IDL_SOURCE:-unknown}"
Step 2: Generate IDL (if needed)
Anchor IDL Generation
if [ "$IDL_SOURCE" = "anchor" ] || [ -f "Anchor.toml" ]; then
echo "Generating Anchor IDL..."
# Build IDL
anchor build
if [ $? -ne 0 ]; then
echo "Anchor build failed. Fix errors before generating client."
exit 1
fi
echo ""
echo "Generated IDL files:"
ls -la target/idl/*.json
# Show IDL summary
for idl in target/idl/*.json; do
PROGRAM=$(basename "$idl" .json)
INSTRUCTIONS=$(grep -c '"name"' "$idl" | head -1)
echo " $PROGRAM: $(cat "$idl" | python3 -c "import sys,json; d=json.load(sys.stdin); print(f'{len(d.get(\"instructions\",[]))} instructions, {len(d.get(\"accounts\",[]))} accounts')" 2>/dev/null || echo "parsed")"
done
fi
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 · 291 lines · 15 tokens per session scan A 62e550308da7
generate-idl-client is a command published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 19d ago), licensed MIT. It adds 15 tokens to every session and 2,178 once invoked, about $0.0001 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 commands, from other repositories
types
Hostile audit of the static type layer: assume every any, every suppression, and every unchecked cast is hiding a real type error until proven otherwise. The type checker is only as strong as the escape hatches punched through it — this command finds every hole.
format
Auto-format code and fix TypeScript issues.
nxt-api-route
Generates a Next.js App Router API route handler (route.ts) with proper TypeScript types, request validation, and error handling. Auto-detects auth patterns from the project.
nxt-component
Generates a Next.js + TypeScript + Tailwind component. Auto-detects project conventions (naming, folder structure, function style) from existing components.
/build-fix
Incrementally fix TypeScript and build errors one at a time, verifying each fix before moving on.
checklist
Generate a custom checklist for the current feature based on user requirements.