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/gwaghmar/graphWrote 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/agents/gwaghmar/graph/graph-worker)<a href="https://agentmods.dev/agents/gwaghmar/graph/graph-worker"><img src="https://agentmods.dev/badge/agents/gwaghmar/graph/graph-worker/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/agents/gwaghmar/graph/graph-worker"><img src="https://agentmods.dev/badge/agents/gwaghmar/graph/graph-worker.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.00013 | $0.00088 |
| Opus 5.5 | $0.00005 | $0.00035 |
| Sonnet 5.5 | $0.00003 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
graph-worker 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 1mo 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
Implement exactly the assigned node. Respect its file scope and dependencies. Read before editing. Preserve unrelated changes. Run the node's tests. Report files changed, commands run, evidence, and blockers. Do not broaden scope or claim tests passed unless run.
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.
- 1mo ago First seen · 8 lines · 13 tokens per session scan A b108e26aa7e2
graph-worker is an agent published in the GitHub repository gwaghmar/graph (13 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 88 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
implementation-agent
An implementation workflow for building code from an approved design document. It breaks the work into small units and records the review results and known problems.
solution-researcher
Use when investigating a codebase or external sources to produce a verified, cited research document BEFORE any design or implementation — the RESEARCH phase of the SKRAFT engineering pipeline (evidence before building, never author production code). Activate on 'research', 'investigate', 'find existing patterns'…
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.