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/open-latch/latchWrote 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/open-latch/latch/latch-gate)<a href="https://agentmods.dev/commands/open-latch/latch/latch-gate"><img src="https://agentmods.dev/badge/commands/open-latch/latch/latch-gate/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/open-latch/latch/latch-gate"><img src="https://agentmods.dev/badge/commands/open-latch/latch/latch-gate.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.00449 |
| Opus 5.5 | $0.00006 | $0.00180 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
latch-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 1mo 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.
What it actually says
Manually invoke the per-project gate (heavyweight LLM go/no-go judgement
layer) for the request in $ARGUMENTS. The primary MCP tool is latch_gate;
kb_gate remains a legacy alias. This slash is the manual escape hatch when
you want an explicit second opinion without relying on auto-invocation.
The classifier returns one of {PROCEED | MODIFY | DO_NOT_PROCEED | NEEDS_HUMAN_JUDGMENT} with cited node ids, a recommended better-next-action, and a side-note summary. It does NOT auto-redirect — the user/agent decides.
Legacy aliases: /kb-gate and kb_gate may exist on older installs and remain
supported for compatibility. Prefer /latch-gate and latch_gate in fresh
instructions and docs.
Budget-gated (counts against the daily LLM cap shared with /latch-compact
and nightly heal). Skip and report the budget message if the cap is hit.
Run
bash <KB_HOME>/bin/run_latch_gate.sh "$ARGUMENTS"
After the command returns, show an explicit Latch gate block. Prefer the
returned findings object; it is already shaped for chat display and should be
shown even when the recommendation is PROCEED or the gate was skipped. If the
result says latch is UNLATCHED, report that latch gate was skipped, do not claim
KB evidence was read, and tell the user to run /unlatch to re-latch. Otherwise,
lead with provenance that Latch ran the gate on the request/plan, then show the
verdict, summary/rationale, receipt / source basis when present, cited evidence
nodes with status/current authority, better_next_action, and uncovered claims.
Don't re-render the full chains object — point the user at the cited ids and
offer to latch_get any of them for full bodies.
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.
- 1mo ago First seen · 38 lines · 15 tokens per session scan A 412931765ac1
latch-gate is a command published in the GitHub repository open-latch/latch (9 stars, last pushed 7d ago), licensed Apache-2.0. It adds 15 tokens to every session and 449 once invoked, about $0.0001 per session on Opus 5.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
ctx
Search agent history or trace code to its original agent session.
handoff-export
Read .claude/skills/handoff/SKILL.md completely and dispatch its export workflow. Use any supplied command arguments only as the requested bundle path; preserve the skill's sourceagent, direct checks, optional verification, and safety boundaries.
handoff
Export a Waybill Bundle by default, or import one when requested.
waybill
Alias that exports by default or imports when requested.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.