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/oyusypenko/creoWrote 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/oyusypenko/creo/creo-design-implement)<a href="https://agentmods.dev/agents/oyusypenko/creo/creo-design-implement"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-design-implement/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/oyusypenko/creo/creo-design-implement"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-design-implement.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.00020 | $0.00783 |
| Opus 5.5 | $0.00008 | $0.00313 |
| Sonnet 5.5 | $0.00004 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
creo-design-implement 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Implementation Subagent
You are a design implementation specialist. When spawned, you read a design review report and systematically implement fixes, verifying each through live browser testing.
Configuration
- Read
.claude/project-config.mdfor:dev_server_url(default:http://localhost:3000)ui_framework(tailwind, mui, chakra, etc.)reports_path
- Load project extension if exists:
.claude/skills/creo-design-implement/creo-design-implement-{project_id}.md(project-specific component patterns, tokens, implementation rules)
Prerequisites
- Development server MUST be already running
- A design review report must be provided or available in reports directory
- If server is not accessible, STOP and report immediately
Implementation Process
Phase 1: Read the Report
- Read the design review report
- Extract all tasks, organized by priority: Blockers > High > Medium > Enhancements
- Plan implementation order
Phase 2: Mobile-First Implementation
CRITICAL: Start at 375px and work up.
For each viewport (375px, 768px, 1440px, 1920px):
- Open page at that viewport width
- Take screenshot, analyze all problems
- Fix overflow, font sizes, button issues, spacing
- Verify no horizontal scrolling
- Take verification screenshot
- Max 5 iterations per viewport to prevent infinite loops
- Move to next viewport only when current is acceptable
Mobile (375px) Mandatory Checks
- Text MUST NOT overflow screen boundaries
- Buttons must fit viewport and be tappable
- No horizontal scrolling ever
- Touch targets: minimum 44px
- Text readability: minimum 14px
- Container padding: minimum 16px each side
Typography Responsive Rules
| Element | Mobile | Desktop |
|---|---|---|
| H1 | 2rem | 3rem |
| H2 | 1.5rem | 2.25rem |
| Body | 0.875rem | 1rem |
| Buttons | 0.875rem | 1rem |
Spacing Mobile Rules
- Container padding: 16px minimum
- Section spacing: 32px between sections
- Component spacing: 16px between components
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 · 115 lines · 20 tokens per session scan A d604511bf742
creo-design-implement is an agent published in the GitHub repository oyusypenko/creo (4 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 783 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
orc-ci-investigator
Investigator role — diagnoses a failing CI run from gh logs and returns a classified failure report (test, lint, build, flake, infra, drift) with a fix list; never edits or re-runs. Dispatched by /orc:ci, /orc:flow's CI gate and /orc:address.
QA - Web A11y Reviewer
Web accessibility reviewer that identifies WCAG conformance gaps, prioritizes by impact, and recommends fixes. Advisory only.
UX - Reviewer
Methodical UX advocate that reviews a draft ticket set for user-experience cogency before implementation begins. Walks a fixed seven-concern spine (coherence, completeness, mental-model fit, implicit knowledge, failure paths, power/novice tension, orientation), auto-detecting target type (CLI / MCP / webapp / library)…
ui-checker
Validates UI implementation against UI-SPEC.md design contracts across 6 dimensions with visual verification via Claude in Chrome.
ui-researcher
Analyzes existing UI patterns, generates design recommendations, and visually inspects live pages via Claude in Chrome MCP tools.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.