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/enmanuelmag/heimdall-mcp/explorergit clone --depth 1 https://github.com/enmanuelmag/heimdall-mcpWrote 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/enmanuelmag/heimdall-mcp/explorer)<a href="https://agentmods.dev/agents/enmanuelmag/heimdall-mcp/explorer"><img src="https://agentmods.dev/badge/agents/enmanuelmag/heimdall-mcp/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.00064 | $0.01091 |
| Opus 5 | $0.00032 | $0.00545 |
| Sonnet 5 | $0.00013 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 141 lines · 64 tokens per session scan A 100bbb086bd0
explorer is an agent published in the GitHub repository enmanuelmag/heimdall-mcp (11 stars, last pushed 1mo ago), with no licence file. It adds 64 tokens to every session and 1,091 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-30.
Other agents, from other repositories
agent-review
Critically review a Stencila agent and suggest improvements. Use when asked to review, audit, critique, evaluate, or improve an agent directory or AGENT.md file. Covers frontmatter validation, system instruction quality, configuration correctness, and adherence to the Agent schema.
clean-implementer
Use this agent when you need to implement a design, feature, or refactor code with an emphasis on clean architecture, testability, and maintainability. This includes writing new modules, refactoring existing code to reduce duplication or complexity, breaking up large files or functions, and organizing code into…
feature-architect
Use this agent when designing new features, planning component interfaces, defining type hierarchies, or architecting abstractions for the codebase. This includes situations where you need to think through API boundaries, module decomposition, dependency management, or type-safe contract design before writing…
agent-reviewer
Reviews an agent for quality, correctness, and completeness.
deployer
Deploys the application to staging. Use when the user asks to push a build to the staging environment.
code-reviewer
Reviews diffs for correctness and security issues. Use after code edits to verify quality before a commit.