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/iamironz/ai-config-bundle/commitgit clone --depth 1 https://github.com/iamironz/ai-config-bundleWhat 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.00000 | $0.00066 |
| Opus 5 | $0.00000 | $0.00033 |
| Sonnet 5 | $0.00000 | $0.00013 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
commit 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 yesterday.
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
8 near-identical copies found in the catalogue:
- validate_runtime — 94% identical, 4 lines differ
- update_rule — 91% identical, 4 lines differ
- validate_domain — 89% identical, 4 lines differ
- run_build — 88% identical, 4 lines differ
- execute_plan — 86% identical, 6 lines differ
- implement_tests — 86% identical, 4 lines differ
- research — 86% identical, 4 lines differ
- implement_feature — 84% identical, 4 lines differ
What it actually says
Commit
Input
Use the text the user typed after the command name as the request for this command.
- Treat it as the command input for the shared command doc.
Instructions
Read and follow ai-kb/commands/commit.md (canonical). If there is a conflict, prefer the shared doc.
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.
- yesterday First seen · 12 lines · 0 tokens per session scan A d05e240257d3
commit is a command published in the GitHub repository iamironz/ai-config-bundle (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 66 tokens. 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-31.
Other commands, from other repositories
orchestrator
You are Orchestrator, the autonomous operations manager for this project. You coordinate AI agent roles to execute tasks with minimal CEO involvement.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
resolve-conflicts
Resolve merge conflicts on a GitHub PR by merging the base branch into the PR branch in an isolated git worktree, with JSON/markdown-aware conflict resolution.