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 commands/solanabr/solana-ai-kit/commit-claude-configgit 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/commit-claude-config)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/commit-claude-config"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/commit-claude-config.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.00035 | $0.00902 |
| Opus 5 | $0.00017 | $0.00451 |
| Sonnet 5 | $0.00007 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
commit-claude-config 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are opting this project into version-controlling its Solana AI Kit config. By default install.sh gitignores the kit (.claude/, CLAUDE.md, .mcp.json, .gitmodules) so it stays out of the user's repo. This command reverses that: it removes the config block from .gitignore, stages those files, and commits them — so the config travels with the repo (team setup, reproducible config).
The ext/ skill submodules stay gitignored (they're upstream content, re-fetched via git submodule update, not vendored). Only .gitmodules is tracked, so the submodule list ships and a --recurse-submodules clone can repopulate them.
Step 0: Preflight
if ! git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
echo "✗ Not a git repository. Run 'git init' first, then re-run /commit-claude-config."
exit 1
fi
# Which config dir is installed?
if [ -d .claude ]; then CONFIG_DIR=.claude
elif [ -d .agents ]; then CONFIG_DIR=.agents
else echo "✗ No .claude/ or .agents/ found — nothing to commit."; exit 1
fi
echo "▸ Config dir: $CONFIG_DIR/"
Step 1: Un-ignore the kit config
Remove the # >>> solana-ai-kit config … <<< block from .gitignore (leaves the ext/ and local-only sections untouched). Portable across GNU/BSD sed via a temp file.
if [ -f .gitignore ] && grep -qF ">>> solana-ai-kit config" .gitignore; then
sed '/# >>> solana-ai-kit config/,/# <<< solana-ai-kit config <<</d' .gitignore > .gitignore.tmp \
&& mv .gitignore.tmp .gitignore
echo "✓ Removed the config block from .gitignore (ext/ + local-only stay ignored)"
else
echo "ℹ config block already absent from .gitignore — continuing"
fi
Step 2: Stage the config
ext/ is still gitignored, so git add "$CONFIG_DIR" records your agents/commands/rules/skills/settings but NOT the 18 upstream submodule trees.
git add .gitignore 2>/dev/null || true
for p in .gitmodules CLAUDE.md .mcp.json "$CONFIG_DIR"; do
[ -e "$p" ] && git add "$p"
done
echo ""
echo "Staged:"
git diff --cached --name-status
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 · 73 lines · 35 tokens per session scan A 8e7287ef4364
commit-claude-config is a command published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 15d ago), licensed MIT. It adds 35 tokens to every session and 902 once invoked, about $0.0002 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
upgrade-project
Update existing project configurations to current best practices with selective component upgrades.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
justify
Audit changes for additive bias, Iron Law compliance, and minimal intervention. Justifies every change against a "simplest safe change" standard.
git-commit
IMPORTANT: This command ONLY runs when explicitly invoked via /git-commit. Do NOT auto-commit after code modifications. Wait for user to explicitly run /git-commit.
git-push
IMPORTANT: This command ONLY runs when explicitly invoked via /git-push. Do NOT auto-push after commits or modifications. Wait for user to explicitly run /push.
commit-smart
Create smart commit with quality checks and conventional format.