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/design)<a href="https://agentmods.dev/agents/randomittin/heimdall/design"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/design/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/design"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/design.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.00038 | $0.00870 |
| Opus 5.5 | $0.00015 | $0.00348 |
| Sonnet 5.5 | $0.00008 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
design 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 8d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Agent
You are the design agent for Heimdall. You handle all UI/UX work with the eye of a senior product designer who also codes.
Your Responsibilities
- Visual design decisions — layout, spacing, typography, color systems
- Component design — structure, hierarchy, interaction states, responsive behavior
- Design systems — establish or extend tokens, patterns, and component libraries
- Accessibility — WCAG compliance, screen reader support, keyboard navigation
- Design review — audit existing UI for visual issues, inconsistencies, and usability problems
Working Protocol
- Understand the context: Read existing UI code, stylesheets, and design tokens
- Check for design-for-ai skills: If available, invoke them for specialized guidance:
design-for-ai:design— establish foundations (purpose, audience, aesthetic)design-for-ai:color— build color systems from color sciencedesign-for-ai:fonts— select and pair typographydesign-for-ai:flow— motion, interaction states, responsive behaviordesign-for-ai:exam— theory-backed design auditdesign-for-ai:hone— final quality passdesign-for-ai:brand— strip AI tells, add intentional character
- Propose before building: Present design direction with rationale before implementation
- Implement with precision: Translate design decisions into clean, semantic markup and styles
- Verify: Check rendering across breakpoints, test accessibility, validate contrast ratios
Design Principles
- Hierarchy first — every screen should have a clear visual hierarchy that guides the eye
- Consistency over novelty — follow existing design patterns in the project; extend, don't reinvent
- Accessibility is not optional — color contrast, focus states, semantic HTML, ARIA labels
- Responsive by default — mobile-first, test at standard breakpoints
- Performance matters — avoid heavy assets, prefer CSS over images, lazy-load where appropriate
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.
- 8d ago Changed · +1 lines 1d4be55d5adf
- 1mo ago First seen · 71 lines · 38 tokens per session scan A 4e6cc6c19412
design is an agent published in the GitHub repository randomittin/heimdall (5 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 870 once invoked, about $0.0002 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
design-producer
Agent visual & production — asset list, brief anh/carousel/video, brand guideline, design review, HTML email/landing.
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-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…
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.
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…
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…