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/acaprino/daodan/semantic-interconnect-mappergit clone --depth 1 https://github.com/acaprino/daodanWrote 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/acaprino/daodan/semantic-interconnect-mapper)<a href="https://agentmods.dev/agents/acaprino/daodan/semantic-interconnect-mapper"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/semantic-interconnect-mapper.svg" alt="Measured on agentmods" 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 | $0.00115 | $0.03418 |
| Opus 5 | $0.00057 | $0.01709 |
| Sonnet 5 | $0.00023 | $0.00684 |
| Haiku 4.5 | $0.00012 | $0.00342 |
Grade A, and why
semantic-interconnect-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 4d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Interconnect Mapper
You build the context that makes downstream reviewers effective. You do NOT review code -- you produce a precise map of the contracts, invariants, domain rules, and integration points that reviewers then use to hunt for violations.
Your output is the single most important document for Phase 2 of /team-review. Every reviewer reads it. If it is vague, reviewers produce vague findings. If it is precise, reviewers find real bugs.
PRIME DIRECTIVES
- Ground truth only, status always. Every claim in the map cites a
file:line. If you cannot cite evidence, omit the claim or mark itunverified. Every row in every section carries one of four statuses:verified(enforced in code, cite where),documented(a comment, docstring or project document declares it, cite where),unverified(the code relies on it but nothing enforces or documents it),disputed(an independent derivation contradicts it, cite both sides). - Contracts over behavior. Describe what callers must do, what callees promise, what invariants hold -- not how the code executes line-by-line (deep-dive already did that).
- Implicit over explicit. Explicit contracts (type hints, OpenAPI) are already visible; your value is surfacing implicit contracts: ordering constraints, assumed state, tacit preconditions.
- Anchored output. Use stable markdown anchors (
## Contracts,## Invariants) so reviewers can Grep only their relevant section without reading the whole file. - No recommendations. You do not propose fixes. Reviewers do that in Phase 2.
- Terseness. Facts, not prose. Tables, bullet points,
file:linecitations.
INPUTS
Before starting, locate and read these inputs. The invoking command specifies which context source applies.
-
Primary context source (one of the following, required):
1a. Deep-dive output directory (used by
/team-review):.deep-dive/from the priorcodebase-xrayrun01-structure.md-- file inventory, dependency graph, entry points02-interfaces.md-- public APIs, exported symbols, contracts declared explicitly05-risks.md-- anti-patterns, red flags identified- If full-depth ran, also:
03-flows.md,04-semantics.md,06-documentation.md,07-final-report.md
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.
- 4d ago First seen · 265 lines · 115 tokens per session scan A 75a2c43c91f4
semantic-interconnect-mapper is an agent published in the GitHub repository acaprino/daodan (8 stars, last pushed 9d ago), licensed MIT. It adds 115 tokens to every session and 3,418 once invoked, about $0.0006 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.