event.exists

A command that checks whether a particular sequence of events exists in a selected branch and space.

In plain words
What is it for?
Use it to test whether an event sequence is present before taking another action.
Why use it?
It confirms existence without returning the matching record.

Command

Install

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.

agentmods
npx agentmods add commands/stratalab/strata-core/event.exists
Clone the repo
git clone --depth 1 https://github.com/stratalab/strata-core
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 53 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00053
Opus 5 $0.00000 $0.00026
Sonnet 5 $0.00000 $0.00011
Haiku 4.5 $0.00000 $0.00005

Measured 2d ago against content hash efcc2e5414b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

event.exists 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.

crates/executor/idl/v1/prose/commands/event.exists.md · 7 lines

What it actually says

Checks whether one event sequence exists in the selected branch and space without returning the record.

Changes

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.

  1. 2d ago First seen · 7 lines · 0 tokens per session scan A efcc2e5414b7

Subscribe to this mod's changes

event.exists is a command published in the GitHub repository stratalab/strata-core (2 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 53 tokens. 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.