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/quantumaikr/quant.cpp/merge-gategit clone --depth 1 https://github.com/quantumaikr/quant.cppWhat 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.00012 | $0.00423 |
| Opus 5 | $0.00006 | $0.00211 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
merge-gate 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 today.
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
Merge Gate
Safely merge completed ClawTeam worker branches into main, reverting any merge that causes a score drop.
Protocol
The team name is: $ARGUMENTS
If no team name provided, list available branches with git branch -a | grep clawteam.
Step 1: Record baseline score
bash score.sh --quick
Save the score as baseline_score.
Step 2: List worker branches
git branch -a | grep "clawteam/$ARGUMENTS"
Step 3: For each worker branch, sequentially:
a. Save current HEAD:
pre_merge=$(git rev-parse HEAD)
b. Attempt merge:
git merge <branch> --no-edit -m "Merge <worker> results"
c. If merge conflict:
git merge --abort
Report: "<worker> has merge conflicts — skipping"
Continue to next worker
d. Score check:
bash score.sh --quick
new_score=$(cat .score)
e. Decision:
If new_score >= baseline_score:
Report: "<worker> merged OK (score: baseline → new_score)"
Update baseline_score = new_score
Else:
Report: "<worker> REVERTED (score dropped: baseline → new_score)"
git reset --hard $pre_merge
Step 4: Final report
- Run
bash score.sh(full evaluation) - Show which workers were merged and which were reverted
- Show final score vs original baseline
- Suggest next action based on new score
Rules
- ALWAYS merge one worker at a time, never batch
- ALWAYS check score after each merge
- ALWAYS revert if score drops — no exceptions
- Order preference: merge simpler modules first (uniform → polar → qjl → turbo → cache → simd → bench)
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.
- today First seen · 70 lines · 12 tokens per session scan A 0c294e05e311
merge-gate is a command published in the GitHub repository quantumaikr/quant.cpp (399 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 423 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-09-01.
Other commands, from other repositories
amk-autoresearch
Launch the unattended / overnight AMK autoresearch driver on $ARGUMENTS (model [gpu] [minutes|iters]).
amk-optimize
Drive an interactive AMK propose -> eval -> keep/revert megakernel schedule session on $ARGUMENTS (model [gpu]).
amk-compile
One-shot compile + verify a model into a CUDA megakernel via amk compile on $ARGUMENTS (model [gpu]).
ARCHITECTURE
Command "ARCHITECTURE" from cloudrift-ai/emmy, covering commands architecture, layered design, layers, emmy/recipe/ — recipe library and emmy/deploy/ — deploy library.
EXPECT
Expect command describes the desired output of the task (after post-processing).
FORMAT
Format command describes the desired output of the task (after post-processing).