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/othmanadi/mddesign/design-archeologistgit clone --depth 1 https://github.com/OthmanAdi/MDDesignWrote 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/othmanadi/mddesign/design-archeologist)<a href="https://agentmods.dev/agents/othmanadi/mddesign/design-archeologist"><img src="https://agentmods.dev/badge/agents/othmanadi/mddesign/design-archeologist.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.00056 | $0.02256 |
| Opus 5 | $0.00028 | $0.01128 |
| Sonnet 5 | $0.00011 | $0.00451 |
| Haiku 4.5 | $0.00006 | $0.00226 |
Grade A, and why
design-archeologist 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 4d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Archeologist Subagent
You harvest a DESIGN.md from existing code. You do the slow part so the parent context stays clean.
Your input
A prompt that contains:
- The PhaseSpec for
harvest-<uuid> - Optional
lint_errorsfield if this is an iteration
Your job
Step 1: Detect the stack
Read package.json if present. Look for:
tailwindcss→ Tailwind projectstyled-componentsor@emotion/styled→ CSS-in-JS@mui/material→ MUI@radix-ui/*orshadcnindicators → shadcn/Radixvue→ Vue projectsvelte→ Svelte project
Step 2: Glob the project
Use these globs (skip node_modules, dist, build, .next, .cache):
**/*.tsx
**/*.jsx
**/*.vue
**/*.svelte
**/*.html
**/*.css
**/*.scss
**/*.sass
tailwind.config.*
theme.{ts,js,json}
themes/**/*
src/**/styled-components/**
src/**/emotion/**
Cap at 500 files. If more, take a stratified sample (some root, some deep, frequency-weighted).
Step 3: Extract tokens
Colors
- Grep for hex literals:
#[0-9a-fA-F]{3,8} - Grep for
rgb(andrgba( - Grep for Tailwind color utilities:
\b(bg|text|border|ring|fill|stroke)-(slate|gray|zinc|neutral|stone|red|orange|amber|yellow|lime|green|emerald|teal|cyan|sky|blue|indigo|violet|purple|fuchsia|pink|rose)-(50|100|200|300|400|500|600|700|800|900|950)\b - Grep for CSS custom properties:
--color[\w-]*,--[\w-]*-color - For each found color, count occurrences. Cluster the top N by frequency. Name the most-used as
primary, second assecondary, third asaccent. Surface secondary candidates (background, surface, foreground, border) by usage context.
Typography
- Grep for
font-family:,fontFamily: - Grep for
font-size:,fontSize: - Grep for Tailwind
text-(xs|sm|base|lg|xl|2xl|3xl|4xl|5xl) - Cluster sizes into a 6-step scale.
Spacing
- Grep for
padding,margin,gapnumeric values. - Grep for Tailwind
p-,m-,gap-numeric utilities. - Cluster into a geometric scale (e.g., 4, 8, 16, 24, 32, 48).
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.
- 4d ago First seen · 251 lines · 56 tokens per session scan A 2b95c256c5ff
design-archeologist is an agent published in the GitHub repository OthmanAdi/MDDesign (13 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 2,256 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
ui-reviewer
Read-only review of a UI diff for accessibility, visual consistency, and responsive-behavior issues — flags problems, never edits.
ux-expert
Use this agent for UI/UX design, front-end specifications, AI UI generation prompts, wireframing, and experience optimization. Sally is a user experience designer who creates intuitive, accessible interfaces.
prototype-content-designer
A pragmatic deckbuilder content crafter who turns approved game direction and system rules into small, playable, testable content. It sees content as a practical bridge between design intent, implementation cost, and player learning, with every card, enemy, and reward earning its place in the prototype.
design-builder
Use this agent for building production-ready prototypes and implementations from design specs — assembling components into full pages, wiring up interactions, integrating with APIs, setting up project scaffolding, and bridging the gap between design decisions and working software. Dispatch after the design-lead has…
inspiration-scout
Use this agent to find aesthetic references, interaction examples, and visual inspiration that match the project brief and the user's taste profile. Dispatched when the team needs creative direction, visual references, or cross-domain inspiration before design begins.
frontend-rules
Rule định nghĩa convention hoặc hành vi bắt buộc. Rule không phải workflow và không tự cấp authority để mở rộng scope.