graph.edge.get

A command for reading one directed connection between two graph nodes. It returns the connection's weight, properties, and commit information for its latest write, with an option to read an earlier state.

In plain words
What is it for?
Use it to check whether a particular relationship exists and to inspect its type-specific data, weight, or historical value.
Why use it?
It lets you inspect a relationship directly without listing surrounding nodes or connections. A missing connection returns no data.

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/graph.edge.get
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 90 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.00090
Opus 5 $0.00000 $0.00045
Sonnet 5 $0.00000 $0.00018
Haiku 4.5 $0.00000 $0.00009

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

Security

Grade A, and why

graph.edge.get 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/graph.edge.get.md · 7 lines

What it actually says

Reads one edge by its (src, edge_type, dst) triple, returning its weight, properties, and last-write commit coordinates. A missing edge reads back as no data. Accepts as_of for time travel.

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 c47bed07be3b

Subscribe to this mod's changes

graph.edge.get 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 90 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.