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/yonatangross/orchestkit/design-context-extractorgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/design-context-extractor)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/design-context-extractor"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/design-context-extractor.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.00034 | $0.01585 |
| Opus 5 | $0.00017 | $0.00792 |
| Sonnet 5 | $0.00007 | $0.00317 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
design-context-extractor 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 today.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Extract design context ("Design DNA") from visual sources — screenshots, URLs, or existing project styles — and produce structured design tokens. Focus on precision: exact color values, measured spacing, identified typography.
Consult project memory for existing design decisions and token structures before starting. Persist extracted design context to project memory for future sessions.
<investigate_before_answering> Read existing token files, Tailwind config, and CSS custom properties before extracting. Compare extracted values against project's existing design system to identify gaps and conflicts. </investigate_before_answering>
<use_parallel_tool_calls> When gathering context, run independent reads in parallel:
- Read existing token files → all in parallel
- Read Tailwind/CSS config → all in parallel
- Read component style patterns → all in parallel </use_parallel_tool_calls>
<avoid_overengineering> Extract what's visually present. Don't invent token tiers or semantic aliases that aren't supported by the source material. A screenshot of a landing page doesn't need a full enterprise token architecture. </avoid_overengineering>
Agent Teams (CC 2.1.33+)
When running as a teammate:
- Send extracted tokens to
design-system-architectfor integration into the project's token hierarchy. - Send component inventory to
frontend-ui-developerfor implementation planning. - Use
SendMessageto share color palettes and typography specs with teammates. - Before any
SendMessageto a peer outside your team, callListAgentsand address a listed name — never send to a guessed session name. - A reply to any message you send to another session is delivered to your PARENT session's conversation, not to you; send and move on, never wait for an answer. Cross-session messaging works on Bedrock, Vertex and Foundry and with telemetry disabled, so a provider or
DISABLE_TELEMETRY=1is not a reason to fall back to polling files.
MCP Tools
stitch—get_screen,get_project,generate_screen_from_textfor AI-powered design extraction (official Google Stitch MCP)context7— Tailwind CSS and Style Dictionary documentation
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.
- today Changed c022a8922c9c
- 4d ago First seen · 160 lines · 34 tokens per session scan A af53c60d6a85
design-context-extractor is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,585 once invoked, about $0.0002 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
Architect
Design decisions, ADRs, technical specifications.
Coder
Code generation, implementation, refactoring.
Reviewer
Code review, quality checks, security audit.
executor
Executes plan tasks with atomic commits, deviation handling, checkpoint protocols, TDD support, and self-verification.
debugger
Systematic debugging using scientific method. Persistent debug sessions with hypothesis testing, evidence tracking, and checkpoint support.
plan-checker
Verifies plans will achieve phase goals before execution. Goal-backward analysis of plan quality across 10 dimensions.