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 skills/open-latch/latch/source-command-latch-pmnpx skills add open-latch/latch --skill source-command-latch-pmgit clone --depth 1 https://github.com/open-latch/latchWhat 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.00065 | $0.00429 |
| Opus 5 | $0.00032 | $0.00215 |
| Sonnet 5 | $0.00013 | $0.00086 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
source-command-latch-pm 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 2d 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
source-command-latch-pm
Use this skill when the user wants the latch PM demo/workflow in Codex: capture one concrete ruled-out decision and show latch's decision-continuity guardrail.
Workflow
-
Read what latch already knows with the available latch KB read tools (
latch_recent/kb_recent, priority listing, and search as needed). Do not re-ask what is already captured. -
Tell the user in one line that you will help seed one decision latch can use to stop a future agent from quietly undoing their judgment.
-
Ask for one concrete approach they already ruled out and why. Good fuel is a specific library, framework, service, architecture, or workflow that another agent might plausibly propose again.
-
If the answer is vague, ask at most one sharpening question. If it is still too vague, fall back to a lightweight project snapshot rather than turning this into an interrogation.
-
Confirm before writing. Render the proposed node with kind, title, body, and any links. On accept/edit, write it with
latch_insert/kb_insertas adecisioninstagingstatus and link it to the current workstream when one is known. Skip means no write. -
After the decision is saved, invite the user to trigger the trip-wire by asking for the rejected path. For the strongest proof, suggest trying it in a fresh session too. When they do, run latch search/gate, cite the stored decision, and redirect with the saved reason.
Keep the payoff focused on decision continuity, not generic project summaries.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 39 lines · 65 tokens per session scan A 9d4c4b991b14
source-command-latch-pm is a skill published in the GitHub repository open-latch/latch (9 stars, last pushed 2d ago), licensed Apache-2.0. It adds 65 tokens to every session and 429 once invoked, about $0.0003 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 skills, from other repositories
weave
Parallel strand orchestration — decompose a task into 3+ independently scoped strands, fan out real subagents (worktree-isolated when they write files), and coordinate through a session file and Insight Capsules. Use ONLY when the user explicitly invokes it by name or slash command.
agentbro-release
Use when releasing AgentBro from this repository: merging dev/main, bumping versions, updating release notes, tagging, pushing, monitoring GitHub Actions, Homebrew cask publication, or fixing a bad release.
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.
mcp-media-inbox-triage
Find media, partnership, and high-intent requests buried in a shared Gmail inbox, summarize the useful ones, and route them to the right owner through Zapier MCP.
customer-deck-builder
Build tailored customer-facing sales or customer success decks from approved account context and generate the presentation with Gamma through Zapier MCP.