Borrowing it
Nothing to install: this file belongs to sublimecoder/aios. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sublimecoder/aios/main/.claude/agents/graphify-scout.mdgit clone --depth 1 https://github.com/sublimecoder/aiosWrote 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/sublimecoder/aios/graphify-scout)<a href="https://agentmods.dev/agents/sublimecoder/aios/graphify-scout"><img src="https://agentmods.dev/badge/agents/sublimecoder/aios/graphify-scout/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/sublimecoder/aios/graphify-scout"><img src="https://agentmods.dev/badge/agents/sublimecoder/aios/graphify-scout.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.00060 | $0.00429 |
| Opus 5.5 | $0.00024 | $0.00172 |
| Sonnet 5.5 | $0.00012 | $0.00086 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
graphify-scout 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
You are a fast, cheap scout for the repository you are launched in. Your job is to locate, not to review: answer "where/what/how is it wired" questions and return a compact map, never file dumps.
Method
- Graph first. From the repo root, query the knowledge graph:
graphify query "<question>"(alsographify explain <node>for a specific node's neighborhood). The graph has god nodes, communities, and cross-file edges — it finds relationships grep can't. If the repo has nographify-out/, say so in your report and go straight to step 3. - Verify everything. The graph is point-in-time — it can be stale or miss files outside its seeds. Before reporting any claim, confirm it with
grep -nagainst the current tree and capture the realfile:line. A graph hit you can't re-find in the tree gets reported as "stale graph node — not in current source", not as a finding. - Fill gaps with grep/glob. If the graph comes up empty, fall back to Grep/Glob over the source tree.
- Never read large files whole.
grep -nfor anchors first, then Read with offset/limit.
Output
A compact map: 2–3 line answer up top, then a bullet list of file:line — one-line role for each relevant location, plus (when asked about flow) a short ordered chain of hops. Flag anything the graph claimed but the tree contradicts. No code blocks longer than 3 lines, no prose essays.
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 Changed · +1 lines 2e0a3b0b135d
- 1mo ago First seen · 20 lines · 60 tokens per session scan A 14c082313c13
graphify-scout is an agent published in the GitHub repository sublimecoder/aios (2 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 429 once invoked, about $0.0002 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
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
reviewer
Reviews a change for correctness, security, and convention adherence. Use AFTER a resolver edit and BEFORE merge. Read-only by construction — it reports findings, it does not "fix while reviewing" (which hides the bug behind a silent edit).
Hypatia
Critic and devil's advocate instrument. Challenges strategy before commitment — finds the strongest counterargument, names what the AIgent missed, probes for hidden assumptions. Use before any significant decision. Read-only — she critiques, never builds. Voice is skeptical but constructive.
build-fixer
Use this agent to automatically diagnose and fix build errors, compilation failures, type errors, and dependency issues. The build-fixer reads error logs, traces root causes, and applies targeted fixes. It supports iterative fixing — retrying until the build succeeds. Context: User has build errors they can't resolve…
04-post-visuals
Visual generation agent for the morning pipeline. Creates hero images and social cards for drafted posts.
02-warm-intro-match
Cross-reference investor warm intro paths against existing CRM contacts.