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/sumulige/sumulige-claude/commitgit clone --depth 1 https://github.com/sumulige/sumulige-claudeWhat 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.00008 | $0.00314 |
| Opus 5 | $0.00004 | $0.00157 |
| Sonnet 5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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.
What it actually says
Create a git commit following best practices.
Step 1: Assess Current State
Run these commands in parallel:
git status
git diff
git log -5 --oneline
Step 2: Stage Changes
- Review what files are changed
- Ask user if all changes should be committed, or if some should be staged separately
- Never commit these patterns:
.env,.env.local, credentialsnode_modules/,dist/,build/.DS_Store,*.log- Any API keys, tokens, or secrets
Step 3: Write Commit Message
Follow this format based on change type:
| Type | Usage |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Code style changes (formatting) |
refactor |
Code refactoring |
test |
Adding or updating tests |
chore |
Build process, tooling |
Commit message template:
<type>: <brief description (50 chars max)>
<detailed explanation if needed>
Co-Authored-By: Claude Opus 4.5 <[email protected]>
Step 4: Create Commit
Use git commit with the message, then run git status to confirm.
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 · 54 lines · 8 tokens per session scan A b8e6aecffb49
commit is a command published in the GitHub repository sumulige/sumulige-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 314 once invoked, about $0.0000 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-31.
Other commands, from other repositories
browser
Inspect and control the current AO session's target-isolated browser. The desktop app must be open. The agent and user share the same live page, cookies, navigation state, and WebContentsView; the runtime remains usable while the Browser panel is hidden. Tabs in this worker share an ephemeral browser profile, while…
spawn
Spawn a worker agent session in a registered project. The session runs the chosen agent in a fresh git worktree. Register the project first with ao project add.
import
Import reads the legacy Agent Orchestrator flat-file store (/.agent-orchestrator) read-only and ports its projects and per-project settings into the rewrite database. Legacy files are never modified, and a re-run skips rows that already exist, so it is safe to run more than once. The daemon must be stopped before…
review
Manage AO code reviews of a worker's PR.
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
work
通过 v3 流程发起正式工作请求 (entry gate).