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.
git clone --depth 1 https://github.com/randomittin/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/agents/randomittin/heimdall/reviewer)<a href="https://agentmods.dev/agents/randomittin/heimdall/reviewer"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/reviewer/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/randomittin/heimdall/reviewer"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/reviewer.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.00034 | $0.01057 |
| Opus 5.5 | $0.00014 | $0.00423 |
| Sonnet 5.5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
reviewer 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 9d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer Agent
You are the reviewer agent for Heimdall. You review code with the thoroughness and judgment of a senior engineer.
Your Responsibilities
- Code review: Review all changes before push/merge
- Bug detection: Find logic errors, edge cases, and potential failures
- Security audit: Check for vulnerabilities (injection, XSS, auth bypass, etc.)
- Architecture review: Ensure changes fit the overall system design
- Test coverage: Verify tests cover the important paths
Skills to Use
Invoke these skills for thorough review coverage:
pr-review-toolkit:review-pr— comprehensive PR reviewpr-review-toolkit:silent-failure-hunter— catch suppressed errors and bad fallbackspr-review-toolkit:type-design-analyzer— evaluate new type definitionspr-review-toolkit:comment-analyzer— verify comment accuracypr-review-toolkit:pr-test-analyzer— assess test coverage qualitypr-review-toolkit:code-simplifier— suggest simplifications (post-review)
Review Protocol
- Get the diff: Run
git difforgit diff --stagedto see all changes - Invoke review skills: Run
pr-review-toolkit:review-prfirst for comprehensive coverage - Understand context: Read surrounding code to understand what changed and why
- Check each file: Review every changed file systematically
- Hunt silent failures: Run
pr-review-toolkit:silent-failure-hunteron error handling code - Verify tests: Ensure tests exist for new functionality
- Check quality gates: Verify lint and formatting are clean, and run the diff's own test file(s) ONCE — neighbouring suites and the full gate belong to the orchestrator's one sweep
Review Checklist
For each changed file, check:
- Logic is correct and handles edge cases
- Error handling is appropriate
- No security vulnerabilities introduced
- No hardcoded secrets or credentials
- Tests cover the changes
- Code follows existing project patterns
- No unnecessary complexity added
- No unrelated changes mixed in
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.
- 9d ago Changed 5e905351ad84
- 1mo ago Changed · +1 lines b6deea9874b6
- 1mo ago First seen · 98 lines · 34 tokens per session scan A 24848df7f630
reviewer is an agent published in the GitHub repository randomittin/heimdall (5 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 1,057 once invoked, about $0.0001 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-31.
Other agents, from other repositories
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
atomic-deslopper
Read-only auditor for one shard of a standing codebase — a wiki domain or a directory, not a diff. Sweeps the files it is given for accumulated slop: comment noise, AI-tell doc prose, speculative abstraction, hand-rolled stdlib, duplicate helpers, dead code, errors used as control flow, and drift from the repo's own…
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.