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.
git clone --depth 1 https://github.com/stratalab/strata-coreWrote 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/stratalab/strata-core/graph.bulk_insert)<a href="https://agentmods.dev/commands/stratalab/strata-core/graph.bulk_insert"><img src="https://agentmods.dev/badge/commands/stratalab/strata-core/graph.bulk_insert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/stratalab/strata-core/graph.bulk_insert"><img src="https://agentmods.dev/badge/commands/stratalab/strata-core/graph.bulk_insert.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00307 |
| Opus 5.5 | $0.00000 | $0.00123 |
| Sonnet 5.5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 25d 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
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.
Each chunk is its own commit, so an interruption leaves the chunks that landed. An import that spans more than one commit sets a durable watermark on the graph with its first commit and clears it with its last: graph meta reports import_pending: true in between, and afterwards if the import was cut short. The watermark says a multi-commit import is in progress, not which payload: it is cleared by whichever graph bulk_insert's last chunk lands next, whatever its chunk size, and ordinary writes leave it as it is. Every row is an upsert, so finishing an interrupted import is re-running its own payload; the graph stays readable and writable throughout.
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.
- 25d ago Changed · +2 lines 383cb417ac61
- 1mo ago First seen · 7 lines · 0 tokens per session scan A cd56c04e64b3
graph.bulk_insert is a command published in the GitHub repository stratalab/strata-core (3 stars, last pushed 17d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 307 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.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
migration
Generate Prisma database migration.
data-models-block
When this command is used, use the following block. Acknowledge your understanding and then await the user's request.
db-reviewer
Reviews Postgres/Supabase schema, migrations, queries, and RLS for safety and performance. Use when DB code changes, before applying a migration, or inside /...