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/pierry/harness-kit/graphgit clone --depth 1 https://github.com/Pierry/harness-kitWhat 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.00020 | $0.00689 |
| Opus 5 | $0.00010 | $0.00345 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
graph 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build graphify knowledge graph for a long-lived target repo. Tree-sitter local for code (no API key). Adds semantic edges via LLM for docs/PDFs/images if present (--with-docs later, v2).
Inputs
- Arg 1 (optional): target repo path (default = cwd)
--update: incremental refresh, merge with existing graph (cheap, fast)--deep: aggressive edge inference (slower, higher fidelity)--wiki: also build wiki-style markdown index
Pre-flight
Run command -v graphify. Missing → block with install hint:
graphify not installed
install: uv tool install graphifyy | pipx install graphifyy | pip install graphifyy
note: PyPI pkg is graphifyy (double y), CLI cmd is graphify
docs: https://github.com/safishamsi/graphify
Steps
- Bash:
.claude/scripts/graph-repo.sh [target] [--update] [--deep] [--wiki] - Script writes
.claude/runtime/cache/graphify/{repo_slug}/graphify-out/ - Outputs
graph.json(queryable),graph.html(interactive),GRAPH_REPORT.md(audit) - Report cache path + open command for graph.html
When to use
- Target repo touched by many features (e.g. main product monorepo): amortize build cost
- Plan stage needs "find all callers of X", "where does Y live", graph query >> grep
- PRP
## 4) Context → Repos and files toucheddiscovery - ~71× token reduction on queries vs raw file reads (per graphify benchmarks)
When NOT to use:
- One-off small repo, overkill
- Hot repo with high commit churn, graph stales fast, use
--updatehook (see Hot-repo section) - No
graphifybinary in env
Reply format
Graph build complete.
target: {target_dir}
slug: {repo_slug}
path: .claude/runtime/cache/graphify/{slug}/graphify-out/
view: open .claude/runtime/cache/graphify/{slug}/graphify-out/graph.html
report: .claude/runtime/cache/graphify/{slug}/graphify-out/GRAPH_REPORT.md
next: /sse:plan + /sse:sdd will consult graph.json when present
Hot-repo: auto-update hook
For frequently-changing target repos, install graphify's git hook:
cd {target_repo} && graphify hook install
Each commit triggers graphify . --update. Graph stays fresh, harness-kit cache reads latest. Document this in target repo's CONTRIBUTING.
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 · 66 lines · 20 tokens per session scan A 7cc45dbda102
graph is a command published in the GitHub repository Pierry/harness-kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 689 once invoked, about $0.0001 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
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.