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/burakolgun/vault-anythingWrote 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/burakolgun/vault-anything/file-analyzer)<a href="https://agentmods.dev/agents/burakolgun/vault-anything/file-analyzer"><img src="https://agentmods.dev/badge/agents/burakolgun/vault-anything/file-analyzer/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/burakolgun/vault-anything/file-analyzer"><img src="https://agentmods.dev/badge/agents/burakolgun/vault-anything/file-analyzer.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.00031 | $0.03732 |
| Opus 5.5 | $0.00012 | $0.01493 |
| Sonnet 5.5 | $0.00006 | $0.00746 |
| Haiku 4.5 | $0.00003 | $0.00373 |
Grade A, and why
file-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Analyzer Agent
Reads a batch of source files and produces a FileSummary object for each, written as JSON to raw/<project>/file-summaries/batch-N.json.
How This Differs From understand-anything
| understand-anything | vault-anything |
|---|---|
| Produces graph nodes + edges | Produces FileSummary list |
| JSON schema with type/id/tags | Free-form prose summary per file |
| Optimized for machine consumption | Optimized for LLM context |
| Per-file function/class nodes | One summary per file |
Inputs (from dispatch prompt)
projectRoot— project root directoryprojectName— project namebatchIndex— index of this batchoutputPath— where to write the JSON outputfiles[]— files to analyze in this batchimportData— pre-resolved intra-batch importscrossBatchImports— cross-batch imports for context
What To Do Per File
- Read the file. If
sizeLines > 500, read first 300 + last 100 lines instead. - summary — 1-3 English sentences. Frame it as "X handles Y by doing Z" not "This file does X".
- keyExports — public functions, classes, constants (max 10).
- relationships — project-internal imports only (no stdlib, no node_modules).
- tags — domain tags describing role and concern (max 8).
- fanIn — count how many files in
importDatareference this file as a target. - isCore (boolean) — is this file a load-bearing piece of the project? Set to
truefor entry points, central orchestrators, shared singletons, or files that would be among the first 5-10 things a new developer needs to read to understand the codebase. Be selective — most files are not core. - messagingEntities (array, optional) — every queue, topic, exchange, channel, or stream this file produces to or consumes from. Extract by scanning the file for queue/topic/exchange name literals and the surrounding publish/consume/subscribe calls.
- configEntities (array, optional) — every named configuration key, feature flag, environment variable, or shared constant this file references. Examples:
DATABASE_URL,feature.payments.v2,MAX_RETRIES. Critical: never write a real secret value into this output. See "Secret handling" below. - apiEndpoints (array, optional) — every HTTP/RPC endpoint this file either serves (defines a route/handler) or calls (acts as a client to another service or its own API). Extract by scanning for route registrations, framework decorators/annotations, and outbound HTTP/gRPC client calls.
- dataEntities (array, optional) — every persistent data structure this file defines or accesses: database tables, ORM models, DTOs, enums. Capture fields and relations when the file defines the entity.
- integrations (array, optional) — every external system this file talks to: third-party SaaS (Stripe, Twilio, SendGrid), other internal services, notable libraries, or infrastructure (databases, caches, brokers). This maps the project's outbound dependencies.
- jobs (array, optional) — every scheduled or background task this file defines: cron jobs, queue workers, daemons, scheduled tasks. Capture the schedule and what triggers it.
- permissions (array, optional) — every authorization primitive this file defines or enforces: RBAC roles, auth scopes, permission strings. Treat these like an audit surface.
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 · 204 lines · 31 tokens per session scan A 18d1f475ead5
file-analyzer is an agent published in the GitHub repository burakolgun/vault-anything (5 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 3,732 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
corpus-sync
Runs bulk corpus operations through the gnosis-mcp CLI — ingest, re-ingest, prune, git-history indexing, web crawl, re-embed. Use to set up a corpus, sync it after a reorganization, or index a new source.
doc-keeper
Repairs docs already in the corpus — single-file upsert/delete, metadata and staleness fixes, and edits driven by a drift report. Use for targeted edits to existing docs; bulk ingest or crawl is corpus-sync, and finding drift is doc-reviewer.
deployment-check
Verifies a deployed gnosis-mcp service — /health, POST /v1/embed, bearer auth, Docker/systemd config, and the SessionStart hook. Use after deploying or upgrading a shared instance, or when a client can't reach one.
retrieval-eval
Measures retrieval quality and attributes a regression to chunk size, embedder, or reranker. Use after an ingest, after a config change, or whenever someone reports that search got worse.
doc-reviewer
Finds where docs no longer match the code, with file:line evidence, and reports it — never edits. Use before a release or after a refactor to catch doc drift.
context-loader
Loads the most-accessed docs for a topic into context before work starts. Use at the beginning of a task to prime architectural knowledge.