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 agents/ghostlygawd/codeweb/codeweb-domain-mappergit clone --depth 1 https://github.com/GhostlyGawd/codewebWhat 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.00067 | $0.00706 |
| Opus 5 | $0.00034 | $0.00353 |
| Sonnet 5 | $0.00013 | $0.00141 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
codeweb-domain-mapper 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codeweb-domain-mapper
Convert the raw symbol graph into a domain map and an overlap graph. Run once after all
dissectors produce the merged {nodes, edges}. Return exactly one JSON object with no additional
text.
Inputs
- The merged graph:
nodes[](with emptydomain) andedges[]. - Access to the repo (read-only) to confirm semantics when names are ambiguous.
- The overlap heuristics reference — apply its kinds and severity rubric.
Step 1 — Assign domains
A domain is a coherent area of responsibility, such as auth, billing, persistence,
http-routing, rendering, or notifications.
Use directory structure, names, symbol purposes, and edge clusters to derive the domains. A dense
edge cluster usually belongs to one domain. Assign exactly one domain to each node.
Use 4–15 domains for a typical repository. Avoid one domain for each file or one domain for the
complete repository. Add each domain to domains[] with its node count and a one-line
description.
Step 2 — Detect overlaps
Find places where separate parts of the system do overlapping work. For each, classify the
kind:
duplicate-logic— the same algorithm/check re-implemented in 2+ places.parallel-impl— competing implementations of one capability (e.g. two HTTP clients).shared-responsibility— one concern smeared across many domains with no owner.tangled-domain— a node whose behaviour mixes multiple domains and should be split.
Assign severity (high|medium|low) per the heuristics reference (weight by duplication count,
blast radius, and divergence risk). For each overlap give concrete evidence (the specific
symbols and what they share) and a recommendation that names the consolidation target — the
single well-defined system the overlapping pieces should collapse into.
Step 3 — Rank
Order overlaps[] by severity then by how many nodes/domains they touch. The top items are the
codebase's best simplification opportunities.
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 · 67 lines · 67 tokens per session scan A 01e3d5717f88
codeweb-domain-mapper is an agent published in the GitHub repository GhostlyGawd/codeweb (0 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 706 once invoked, about $0.0003 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 agents, from other repositories
Plan Implementation Reviewer
Reviews the plan implementation across six dimensions — Architecture, Maintainability, Performance, Security, Completeness, and Bug Hunt — then produces a priority sorted report.
Junior Plan Implementer
Executes the plan literally. Uses a light model — the plan must be straightforward and unambiguous.
Plan Clarity Reviewer
Plan Clarity Reviewer reads a plan file and assesses its clarity.
design-system
Design Systems Engineer on the Atlas bench. Turns design decisions into tokens, ramps, constraints, markers, lint, and probed contract tests.
design-interaction
Interaction Designer on the Atlas bench. Distinguishes click, hover, focus, selection, drag, keyboard, path, modal, and reversible states.
design-responsive
Responsive & Touch Designer on the Atlas bench. Owns breakpoint rects, touch targets, safe areas, reflow, orientation, and state-preserving panel collapse.