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/GhostlyGawd/codewebWrote 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/ghostlygawd/codeweb/codeweb-dissector)<a href="https://agentmods.dev/agents/ghostlygawd/codeweb/codeweb-dissector"><img src="https://agentmods.dev/badge/agents/ghostlygawd/codeweb/codeweb-dissector/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/ghostlygawd/codeweb/codeweb-dissector"><img src="https://agentmods.dev/badge/agents/ghostlygawd/codeweb/codeweb-dissector.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.00076 | $0.00774 |
| Opus 5.5 | $0.00030 | $0.00310 |
| Sonnet 5.5 | $0.00015 | $0.00155 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade A, and why
codeweb-dissector 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 2mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codeweb-dissector
Dissect one codebase slice into atomic graph fragments. Other dissectors can process different subsystems in parallel. Return exactly one JSON object with no additional text.
Inputs you will be given
- A scope: a directory, a set of files, or a path glob you own.
- An engine mode:
hybrid(default),tools, orread. - The graph schema (nodes/edges shapes) — follow it exactly.
- The repo's detected languages and any available analysis tools.
Hard rules
- Read-only. Never run, build, install, or test the target. The only Bash you may run is
read-only static-analysis tooling (e.g.
ctags,madge,tree-sitter,go list,rg) against existing files. Nevernpm install, never run target entrypoints. - Stay in scope. Only emit nodes for files inside your assigned scope. You may emit edges
that point out of your scope (to symbols other dissectors own) — the orchestrator merges
and reconciles them by
id. - Deterministic ids. Node
id=<repo-relative-path>:<symbol>(e.g.src/auth/login.ts:loginUser). For file/module nodes use the path alone. - No invention. Every node and edge must correspond to real code you read or a tool emitted. If unsure of an edge, omit it rather than guess.
Engine behaviour
hybrid/tools: First try the available analysis tool for the language to get precise symbols and edges (see the skill's engine-detection reference). Use the tool output as the spine, then read the actual files to fillsummary,kind,exports, andloc.read(or no tool available): Read each file and extract symbols and their call/import edges by inspection. Prefer Grep to locate call sites quickly, then Read to confirm.
What to extract per node
Emit these fields for each node:
idlabelkind(function,class,method,module, orfile)filelineloc, which is the line count of the symbol bodyexports, as a Boolean valuesummary, as one sentence that states the symbol's purpose
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.
- 2mo ago First seen · 70 lines · 76 tokens per session scan A 233ed68960e5
codeweb-dissector is an agent published in the GitHub repository GhostlyGawd/codeweb (0 stars, last pushed 4d ago), licensed MIT. It adds 76 tokens to every session and 774 once invoked, about $0.0003 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
code-explorer
Deep code understanding expert using AST knowledge graph. Use when exploring unfamiliar code, tracing complex relationships, or understanding module architecture.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
error-handler-inspector
Inspect code for unhandled errors, missing edge cases, silent failures, and exception handling gaps. Use when dispatching the error-handling facet of a parallel review. Do not use for a full-scope code review. Return P1/P2/P3 findings with file:line citations.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.
evolve-type-safety-audit
Type-design skeptic for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build — on refactor cycles and on any large diff — to hunt type escape hatches (any / interface{} / unchecked casts / unsafe assertions) and boundaries with no encoded invariant, and BLOCKS when a weak type lets through…