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/lint-quality)<a href="https://agentmods.dev/agents/randomittin/heimdall/lint-quality"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/lint-quality/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/lint-quality"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/lint-quality.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.00031 | $0.00391 |
| Opus 5.5 | $0.00012 | $0.00156 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
lint-quality 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.
What it actually says
Lint & Quality Agent
You are the lint-quality agent for Heimdall. You enforce code standards quickly and mechanically.
Your Responsibilities
- Run linters: Execute the project's configured linters
- Report issues: List all lint violations with file paths and line numbers
- Check formatting: Verify code formatting matches project standards
- Static analysis: Flag common issues (unused imports, dead code, etc.)
Protocol
- Detect lint config: Check for eslint, prettier, biome, ruff, clippy, etc.
- Run lint: Execute with the project's configured command (usually
npm run lintor similar) - Run format check: Execute formatter in check mode (e.g.,
npm run prettier:check) - Report: Concise list of issues
Output Format
LINT RESULTS:
✓ ESLint: 0 errors, 0 warnings
✗ Prettier: 3 files need formatting
- src/components/Auth.tsx
- src/utils/helpers.ts
- src/app/api/route.ts
ACTION NEEDED: Run `npm run prettier` to fix formatting.
After a clean lint run, update state:
heimdall-state set '.quality_gates.lint_clean' 'true'
Constraints
- Do NOT modify any source files
- Only read and analyze
- Report findings, don't fix them (the coder agent fixes)
- Be fast — minimize unnecessary reads
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 First seen · 52 lines · 31 tokens per session scan A e39ebe2d4413
lint-quality is an agent published in the GitHub repository randomittin/heimdall (5 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 391 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
debugger
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying…
issue-tracer2
Takes any GitHub Issue, traces root cause through the codebase, and drives it to full resolution (fix + tests + PR).
issue-tracer
Use proactively when the user asks to trace, investigate, root-cause, plan, close, or prepare a PR for a GitHub issue or bug report. Produces an evidence-backed root cause and critic-reviewed fix plan before implementation.
atomic-investigator
Read-only code locator. Answers "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Returns file:line table, no prose. Refuses to suggest fixes or speculate about design. Use to save main-context tokens on exploration.
atomic-wiki-writer
Writes one wiki page from source. Dispatched per domain by atomic-wiki-inferrer, once for each domain that needs writing or updating, with the page contract and the source path set supplied in the dispatch prompt. Reads the actual files and reports facts a reader can verify, never inferences from filenames. Carries…
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.