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/synaptiai/synapti-marketplace/triggergit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/trigger)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/trigger"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/trigger.svg" alt="Measured on agentmods" 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 | $0.00049 | $0.01130 |
| Opus 5 | $0.00024 | $0.00565 |
| Sonnet 5 | $0.00010 | $0.00226 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
trigger 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/flow:trigger — FlowTrigger management
Flow cannot invoke native /loop, scheduled tasks, or any external runner from plugin code. FlowTrigger artifacts at .flow/triggers/<id>.trigger.yaml describe wake-up intent — they declare when flow SHOULD resume work and what command to invoke, but actual execution requires manual user invocation (v3.0: manual | hook | loop_prompt) or an external runner (v3.1+: github_actions | local_cron).
Required Skills
trigger-policy— every subcommand that creates / enables / runs a trigger.
Pre-flight
ENABLED=$("$(__fr="${CLAUDE_PLUGIN_ROOT:-}";[ -x "$__fr/bin/cascade-resolve.sh" ]||__fr=$({ echo plugins/flow;ls -d "$HOME"/.claude/plugins/cache/synapti-marketplace/flow/*/ 2>/dev/null|sort -Vr;echo "$HOME/.claude/plugins/marketplaces/synapti-marketplace/plugins/flow"; }|while read -r __p;do [ -x "${__p%/}/bin/cascade-resolve.sh" ]&&{ echo "${__p%/}";break;};done);echo "$__fr")/bin/cascade-resolve.sh" \
--default "false" '.flow.triggers.enabled')
if [ "$ENABLED" != "true" ]; then
echo "flow.triggers.enabled is false — /flow:trigger is opt-in." >&2
echo "Enable in .claude/settings.flow.local.json: { \"flow\": { \"triggers\": { \"enabled\": true } } }"
exit 0
fi
mkdir -p .flow/triggers
Subcommands
/flow:trigger list
List all triggers (plugin-shipped templates + project-local).
/flow:trigger inspect <id>
Print the trigger YAML's full contents.
/flow:trigger enable <id> / /flow:trigger disable <id>
Toggle metadata.enabled in the trigger YAML. Atomic via _journal_atomic.py lock acquisition.
Before enabling: invoke Skill(trigger-policy) in validate mode. Refuse to enable if policy violations exist.
/flow:trigger run <id>
Execute the target command ONCE. Does NOT schedule future execution. Sequence:
- Invoke
Skill(trigger-policy)inenforcemode. Abort on policy violation. - Check
concurrency.policy— ifskip_if_runningand a prior run is in flight, exit 0 with a notice. - Set the env var
FLOW_TRIGGERED_RUN=trueso the target command knows it was trigger-fired (recursion_policy applies). - Invoke
target.command(e.g.,/flow:run trigger pr-123-watchwhich itself delegates to the trigger's workflow). - Append a
trigger-firedartifact to the linked decision journal.
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 · 82 lines · 49 tokens per session scan A 6f12602360a7
trigger is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,130 once invoked, about $0.0002 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-03.
Other commands, from other repositories
create-worktree
Follow these steps to create a git worktree.
hf.audit-tests
Run a comprehensive test quality audit across the entire repo. Analyzes test naming, structure, hygiene, factory usage, fluent builder patterns, anti-patterns, coverage gaps, and flaky patterns. Creates GitHub issues for findings so HydraFlow can process them.
hf.issue
Take a rough description from the user, research the relevant codebase, and create a well-structured GitHub issue with full context, file references, and acceptance criteria.
write
Launch a writing-mode agent team.
hf.memory
Scan the current conversation for architectural decisions, bug root causes, configuration choices, codebase patterns, and workflow preferences. Write each as a memory item to the local JSONL store for ingestion by the memory sync worker.
paper-trail-review
Review and arbitrate problematic references (cascade-exhausted, unresolved UID, awaiting OCR). Generates an up-to-date report, walks through cases by category, and applies arbitration decisions to the registry.