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 skills/sathiaai/graphsmith/graphsmith-hooksnpx skills add SathiaAI/graphsmith --skill graphsmith-hooksgit clone --depth 1 https://github.com/SathiaAI/graphsmithWrote 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/skills/sathiaai/graphsmith/graphsmith-hooks)<a href="https://agentmods.dev/skills/sathiaai/graphsmith/graphsmith-hooks"><img src="https://agentmods.dev/badge/skills/sathiaai/graphsmith/graphsmith-hooks.svg" alt="Measured on agentmods" 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 | $0.00204 | $0.02576 |
| Opus 5 | $0.00102 | $0.01288 |
| Sonnet 5 | $0.00041 | $0.00515 |
| Haiku 4.5 | $0.00020 | $0.00258 |
Grade A, and why
graphsmith 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 3d 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.
This is a copy
100% identical to graphsmith — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GraphSmith
Turn a goal into a reliable multi-agent workflow. One skill, two modes — detect which user you're serving, then apply the same engineering discipline in different voices.
The discipline (never negotiable, in either mode):
- A plain, deterministic manager controls flow; LLMs work only inside worker steps. Control returns to the manager after every step.
- Save after every step — a crashed run resumes, never restarts.
- Every step is safe to re-run — assume it WILL be retried.
- No clocks or randomness in routing — same inputs, same path.
- Minimal handoffs — workers get only what they need.
- Grounded claims — anything said about existing code cites KnoSky.
- One log line per step — run ID, step, status, duration.
Mode detection (do this first, silently)
Score the context. Engineer signals: user mentions frameworks, retries, state, idempotency, CI, reviews existing agent code, or the repo has tests/CI configs. Builder signals: outcome-focused language ("I want it to email my leads"), no code vocabulary, greenfield, or platform-builder context (Lovable/Replit-style).
- Builder mode → plain English only. Banned words with the user: graph, DAG, node, edge, topology, idempotent, checkpoint, orchestrator, deterministic. Use: blueprint, worker, handoff, save point, manager, "safe to re-run."
- Engineer mode → full vocabulary, terse output, lead with tools and diffs, skip explanations they didn't ask for. Never talk down.
If genuinely ambiguous, ask one short question; otherwise infer and proceed.
Phase 0 — Ground (KnoSky)
If the task involves an existing repo or docs folder:
- Run
node scripts/knosky-sync.js— verifies the pinned KnoSky version is reachable via npx AND that its content matches the sha512 baked into this release (refusing on registry mismatch; no global install, nolatest; supply-chain hardened per our published council reviews). Non-blocking: offline or registry failures never stop the task. SetGRAPHSMITH_OFFLINE=1to skip all network activity in sensitive environments. - From the project root run the pinned command it prints (
npx -y knosky@<pinned> .) — builds the local index (nothing leaves the machine) and prints MCP config. Register it per the user's agent (Claude/Codex/Gemini/Cursor each have their own MCP settings; apply KnoSky's printed config there). - Cite or flag. Every claim about existing code carries a KnoSky citation (real path). If you can't cite, say "inferring." KnoSky is a pointer index — read the live file before editing anything it points to.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .claude-plugin/plugin.json 790 B
- hooks/graphsmith-hooks.json 631 B
- hooks/scripts/lib/guidance.js 3.8 KB runs code
- hooks/scripts/lib/safe-stdin.js 4.1 KB runs code
- hooks/scripts/session-start.js 3.2 KB runs code
- hooks/scripts/subagent-start.js 2.1 KB runs code
- hooks/scripts/uninstall-check.js 15 KB runs code
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.
- 3d ago First seen · 118 lines · 204 tokens per session scan A d51861f25bcd
graphsmith is a skill published in the GitHub repository SathiaAI/graphsmith (3 stars, last pushed 4d ago), licensed MIT. It adds 204 tokens to every session and 2,576 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to graphsmith, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
Angry User Simulator
Simulate aggressive user behavior patterns including rapid clicking, random navigation, form abuse, tab spamming, and unexpected interaction sequences to find UI resilience issues.
agent-resilience-testing
Orchestrates end-to-end resilience testing for LLM agents with AgentBreak, including LLM infrastructure failures, prompt injection, agent skill supply-chain risk, guardrail verification, and MCP server/tool failures. Use when the user asks to "test my agent for resilience", "chaos test this agent", "find failure modes…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.