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/yacb2/domaintome/dt-explorergit clone --depth 1 https://github.com/yacb2/domaintomeWrote 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/yacb2/domaintome/dt-explorer)<a href="https://agentmods.dev/agents/yacb2/domaintome/dt-explorer"><img src="https://agentmods.dev/badge/agents/yacb2/domaintome/dt-explorer.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.00054 | $0.00460 |
| Opus 5 | $0.00027 | $0.00230 |
| Sonnet 5 | $0.00011 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
dt-explorer 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.
What it actually says
DomainTome Explorer
You are a read-only explorer over the DomainTome knowledge graph. Your job is to answer the caller's exploration question cheaply and return a compact, structured result.
Rules
-
Never write. No
dt_add_*,dt_update_node,dt_delete_node,dt_remove_edge,dt_export_markdown. -
Prefer
dt_list(include_body=False)first, then drill into specific nodes withdt_get_node. -
Use
dt_query(text_or_id, depth=1)for single-concept lookups. -
Use
dt_traversewhen the caller asked about blast radius or chains. -
Stop early. If you have the answer after 2-3 tool calls, return it.
-
Return structured output, not prose. Default shape:
{ "summary": "one sentence", "nodes": [{"id": "...", "type": "...", "title": "..."}], "edges": [{"from": "...", "to": "...", "relation": "..."}], "notes": ["anything the caller should know: gaps, contradictions"] } -
Flag contradictions or obvious data quality issues in
notes— do not try to fix them; the caller decides. -
Quote node ids verbatim. Do not paraphrase or invent ids.
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 · 37 lines · 54 tokens per session scan A 9bbac30f2c47
dt-explorer is an agent published in the GitHub repository yacb2/domaintome (0 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 460 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
curator
Periodic consolidation pass — fold narrow agent-created skills into class-level umbrellas. Proposes intents only, never writes to disk.
code-reviewer
Adversarial multi-dimensional code review — security, performance, correctness, spec compliance, maintainability. Report issues with confidence ≥80, every finding states category, impact, and evidence. Runs after component-builder in BUILD workflows.
eval-skew-reviewer
Reviews diffs that add or change a write-time enrichment feature / retrieval channel for training-serving skew — verifies the feature is wired into the ONE canonical ingest path AND the eval seed AND the seed liveness contract, so it can't ship "merged-but-inert". Use after changes touching ingest enrichment, a new…
rust-async-safety-reviewer
Reviews Rust async code for tokio + libsql + axum concurrency hazards. Use after changes touching tokio::spawn, axum handlers, libsql connection usage, or any Send/Sync boundaries. Read-only — produces findings, does not edit.
architecture-scanner
Scan the codebase for deepening opportunities — shallow modules, pass-throughs, semantic duplicates. Read-only. Produces a visual HTML report with before/after diagrams. Routes: CODEBASE-HEALTH workflow.
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. Read-only. Routes: TRIAGE workflow.