Borrowing it
Nothing to install: this file belongs to dbcls/togomcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dbcls/togomcp/main/.claude/agents/mie-builder.mdgit clone --depth 1 https://github.com/dbcls/togomcpWrote 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/dbcls/togomcp/mie-builder)<a href="https://agentmods.dev/agents/dbcls/togomcp/mie-builder"><img src="https://agentmods.dev/badge/agents/dbcls/togomcp/mie-builder/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/dbcls/togomcp/mie-builder"><img src="https://agentmods.dev/badge/agents/dbcls/togomcp/mie-builder.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.00117 | $0.01172 |
| Opus 5.5 | $0.00047 | $0.00469 |
| Sonnet 5.5 | $0.00023 | $0.00234 |
| Haiku 4.5 | $0.00012 | $0.00117 |
Grade A, and why
mie-builder 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You build or revise exactly ONE MIE file for the database named in your prompt. You are a delegated worker: your final message is consumed by an orchestrator, not shown to a human, so it must be terse and machine-checkable — NOT a chat reply.
Procedure — follow the skill, do not improvise
- The mie-generator
SKILL.mdshould be preloaded into your context (via theskills:frontmatter). If it is NOT already in your context,Read .claude/skills/mie-generator/SKILL.mdfirst. It is the canonical procedure — follow every phase (0–6) exactly; do not shortcut it from memory. Either way, read itsreferences/files too (query-strategy.md,mie-structure.md,template.yaml,anti-patterns.md), which are NOT preloaded. - Load the live tools you need via ToolSearch, e.g.
select:mcp__togomcp-dev__run_sparql,mcp__togomcp-dev__get_graph_list,mcp__togomcp-dev__get_sparql_endpoints. Use the togomcp-dev server (local stdio) — it picks up freshendpoints.csvrows; the remote server has a stale registry. If your prompt names a different server, use that instead. The discovery trio (find_databases/list_databases/list_categories) is retired — do not load or call it; for the category vocabulary runscripts/generate_usage_guide_catalog.py --list-categories. - Existing MIE under
togo_mcp/data/mie/<db>.yamlis a HINT to verify, never a source of truth — including its graph list. It may still be a v2 file (pre-redesign layout); you are authoring v3 (togo_mcp/data/docs/MIE_v3_spec.md), so treat its structure as legacy, not a template. Phase 2a (get_graph_list) is mandatory every run. - Write the file directly with Write/Edit.
get_MIE_file/save_MIE_fileare not used here.
The two hard rules (non-negotiable — you will be re-validated)
- No blind retry loops. If a query fails twice, diagnose (wrong predicate / graph / IRI / literal typing) before retrying. More retries without diagnosis do not fix a structurally wrong query.
- Nothing invented. Every
examples[].sparql(including the elevatedaggregationandcross_dbones) and everyentity_countsnumber must be retrieved from the live endpoint before the file is written, its result recorded in the example'sverified:block with adate:(neveron:— YAML parses that as booleantrue) and at least one asserted key (n/row_count/min_rows/has_values, spec §4.1);uv run python scripts/check_mie_examples.py <db>must report 0 zero-row / error / drift / malformed. A fabricated-but-plausible example is the worst possible output: an independent validator WILL re-run your queries against the endpoint, and a false "validated" claim is a hard failure. Never report a check as passed unless you actually ran it and saw it pass.
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 Changed · +2 lines 7c26e867c603
- 2mo ago First seen · 67 lines · 117 tokens per session scan A e5c9d2960024
mie-builder is an agent published in the GitHub repository dbcls/togomcp (20 stars, last pushed 2d ago), licensed MIT. It adds 117 tokens to every session and 1,172 once invoked, about $0.0005 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-30.
Other agents, from other repositories
context-builder
Context capture and knowledge structuring specialist. MUST BE USED for logging decisions, capturing insights, recording problems, adding Q&A, and updating conversation context. Use PROACTIVELY when important information should be remembered.
knowledge-analyst
Deep analysis and insight extraction expert. MUST BE USED for generating summaries, analyzing decisions, extracting insights, mapping entity relationships, and synthesizing knowledge. Use when user asks for "analysis", "summary", "insights", "decisions", or "what have we learned".
memory-curator
Session and workspace management specialist. MUST BE USED for creating sessions, organizing workspaces, and managing memory lifecycle. Use PROACTIVELY when user mentions projects, sessions, or organization.
search-specialist
Semantic and keyword search expert. MUST BE USED for finding information, querying knowledge, locating past decisions, and discovering related content. Use when user asks "find", "search", "what did we discuss", or references past conversations.
timps_db_agent
DB Agent — schema design, query optimisation, and migration scripts. Given a description of your data model it produces: CREATE TABLE SQL, an ER diagram in Mermaid, index recommendations, a migration script (Alembic / Flyway / raw SQL), and query templates. Pairs with the sqlinjection LoRA for secure query generation.…
timps_vector_db_agent
Design Qdrant/Pinecone/Weaviate/pgvector schemas and integration code. Use the timpsvectordbagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.