graph.bulk_insert

A command that loads many graph nodes and relationships in bounded groups. Nodes are inserted before edges so relationships can refer to nodes in the same submission.

In plain words
What is it for?
Use it to ingest batches of nodes and edges, with optional relationship weights and properties.
Why use it?
It makes large graph imports manageable by splitting them into smaller database commits and reporting what was inserted.

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.bulk_insert
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 160 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.00160
Opus 5 $0.00000 $0.00080
Sonnet 5 $0.00000 $0.00032
Haiku 4.5 $0.00000 $0.00016

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

Security

Grade A, and why

graph.bulk_insert 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.

crates/executor/idl/v1/prose/commands/graph.bulk_insert.md · 7 lines

What it actually says

Ingests a payload of nodes and edges in chunked commits: nodes first, then edges, so edges may reference nodes from the same payload. Node objects use the key node_id; edges use src, edge_type, dst, and optional weight (default 1.0) and properties. chunk_size bounds items per commit (default 512, clamped at 800). The acknowledgement reports inserted counts, the number of chunk commits, and the final chunk's commit receipt.

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. yesterday First seen · 7 lines · 0 tokens per session scan A cd56c04e64b3

Subscribe to this mod's changes

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