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 skills add caglarbozkurt/mcp-heimdall --skill skillgit clone --depth 1 https://github.com/caglarbozkurt/mcp-heimdallWrote 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/skills/caglarbozkurt/mcp-heimdall/skill)<a href="https://agentmods.dev/skills/caglarbozkurt/mcp-heimdall/skill"><img src="https://agentmods.dev/badge/skills/caglarbozkurt/mcp-heimdall/skill/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/skills/caglarbozkurt/mcp-heimdall/skill"><img src="https://agentmods.dev/badge/skills/caglarbozkurt/mcp-heimdall/skill.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.00071 | $0.00610 |
| Opus 5 | $0.00036 | $0.00305 |
| Sonnet 5 | $0.00014 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
heimdall 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- heimdall — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Heimdall
Run a security scan on an MCP server and report the risk.
When to use
The user is about to install/connect an MCP server and wants to know if it's safe,
or asks to "audit / scan / vet / check" an MCP, or pasted a tools/list output and
asked whether the tool descriptions look poisoned.
How to run
From the Heimdall project directory:
# local server directory
npx tsx src/cli.ts <path-to-server>
# npm package, PyPI package (pypi:name), GitHub URL, or a tools/list JSON dump
npx tsx src/cli.ts <npm-package | pypi:name | github-url | tools.json>
# machine-readable
npx tsx src/cli.ts <target> --json
# also check the server's dependencies for known CVEs (queries OSV.dev over the network)
npx tsx src/cli.ts <target> --online
If installed globally / as a dependency, use heimdall <target> instead.
Add --online when the user wants supply-chain coverage: it checks declared dependencies
against the OSV.dev advisory database and reports real CVE IDs. It sends only dependency
names + versions (never source); leave it off to stay fully offline.
For a behavioral cross-check, heimdall validate <target> runs the server and calls its
tools to observe what it actually does, then compares that to the static flags (confirmed
/ missed / not-exercised). It executes untrusted code with side effects — only suggest it in
a disposable VM/container, never on the user's real machine.
To analyze injection with full fidelity when tool descriptions can't be read from
source, capture the server's tools/list output to a file and pass --tools <file>.
Interpreting the result
- verdict:
pass/warn/fail. Any hard [GATE] finding forcesfail. - risk score: 0 (clean) – 100 (worst).
- fingerprint: stable hash of the tool surface. Save it; if it changes on a later scan, the MCP silently altered its tools (possible rug-pull).
Summarize the gates and highest-severity findings for the user, cite the evidence
(file:line or tool:name), and give a clear install / don't-install recommendation.
Never recommend installing a server with an unresolved GATE finding.
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.
- 10d ago First seen · 58 lines · 71 tokens per session scan A 2449c39be61c
heimdall is a skill published in the GitHub repository caglarbozkurt/mcp-heimdall (0 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 610 once invoked, about $0.0004 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 skills, from other repositories
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
lc-curate-context
Decide which files a task actually needs, record that as a reusable llm-context rule, verify it against the codebase - including the files your selection references but leaves out - and pack it for your own context, a chat, or a sub-agent you dispatch. Load when choosing what code to put in front of a model, packing…
agent-safety
Use when bounding an LLM agent that already runs — scoping its task domain, gating tools to least privilege, defending against prompt injection in untrusted web/email/RAG text, requiring human approval on irreversible actions, capping runtime and cost, or triaging what it already did. NOT building the loop, tools, or…
dialectos
Use DialectOS for Spanish dialect translation, localization QA, i18n locale-file validation, glossary enforcement, register/formality checks, gender-neutral language, and launch certification across regional Spanish variants through MCP or CLI.
cvx
Create, validate, and render professional CV/resume PDFs from plain YAML using CVX — fully local, no accounts. Use when the user wants to write a CV or resume, convert an existing CV to a maintained format, tailor a CV for a job application, or produce an ATS-safe variant. Covers the cv-content/ YAML schema, the…
zenith
Author, edit, and render deterministic .zen design documents (posters, decks/slides, social graphics, flyers, books, magazines, diagrams, ads) with the zenith CLI. Use when the task is to create or change a visual design as structured, editable, version-controllable source — not a flat AI image. Covers: design tokens…