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/sciencemj/graph-engineering/graph-statusgit clone --depth 1 https://github.com/sciencemj/graph-engineeringWhat 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.00007 | $0.00228 |
| Opus 5 | $0.00003 | $0.00114 |
| Sonnet 5 | $0.00001 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
graph-status 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.
What it actually says
Target: $ARGUMENTS (everything, if empty)
graph_listfor the graphs and their lock state.run_listfor the runs. If a specific run was named, get the detail withrun_get_context.- Summarize in a table:
- each node's status (
pending/ready/running/awaiting_*/succeeded/failed/skipped) with itsvisitandattempt - where the cursor is and what it is waiting on (
waiting_for) last_advance_at— when the cursor was last pushed
- each node's status (
- If
waiting_foris"user", say what the user has to do. If it is"ai_pump", say that/graph-engineering:graph-runcan keep pushing it.
If a node failed, read the cause with run_get_node_log and report it too.
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 · 19 lines · 7 tokens per session scan A 87296a08af29
graph-status is a command published in the GitHub repository sciencemj/graph-engineering (0 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 228 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
triage
Classify/label newly opened GitHub issues missing labels.
release
Release all packages at specified version.
cleanup
Autonomous cleanup-loop iteration: discover ONE target → complete execution → verify → report. Runs stateless: derive from current tree; assume prior runs left it consistent.
hello
Say hello.