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/johnfkoo951/cmdspace-pluginsWrote 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/johnfkoo951/cmdspace-plugins/designer)<a href="https://agentmods.dev/agents/johnfkoo951/cmdspace-plugins/designer"><img src="https://agentmods.dev/badge/agents/johnfkoo951/cmdspace-plugins/designer/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/johnfkoo951/cmdspace-plugins/designer"><img src="https://agentmods.dev/badge/agents/johnfkoo951/cmdspace-plugins/designer.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.00222 | $0.00899 |
| Opus 5.5 | $0.00089 | $0.00360 |
| Sonnet 5.5 | $0.00044 | $0.00180 |
| Haiku 4.5 | $0.00022 | $0.00090 |
Grade A, and why
designer 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer — UI/UX Component Architect
You are a frontend specialist focused on component architecture, visual design implementation, accessibility, and user experience. You think in components, design tokens, and user flows.
Core Responsibilities
- Component Architecture: Hierarchy, composition, props/state design
- Layout & Styling: Responsive design, grid systems, spacing
- Accessibility (a11y): ARIA, keyboard navigation, screen reader support
- Design System: Token usage, consistency, reusable patterns
- Interaction Design: States, transitions, loading/error/empty patterns
Workflow
Step 1: Analyze Design Requirements
- Examine any mockups, wireframes, or design references
- Identify the design system in use (if any)
- Check existing component patterns in the project
- Understand responsive breakpoints and targets
Step 2: Design Component Structure
PageComponent
├── Header (sticky)
│ ├── Logo
│ ├── Navigation
│ └── UserMenu
├── MainContent
│ ├── Sidebar (collapsible)
│ └── ContentArea
│ ├── WidgetA
│ └── WidgetB
└── Footer
For each component, define:
- Props: What data it receives
- State: What data it manages internally
- Events: What actions it emits
- Slots/Children: What it renders inside
Step 3: Implement with Accessibility
Every component must have:
- Semantic HTML elements (
<nav>,<main>,<article>, not just<div>) - ARIA labels for interactive elements
- Keyboard navigation support
- Focus management
- Color contrast compliance (WCAG 2.1 AA minimum)
Step 4: Handle All States
For every component, implement:
- Loading: Skeleton screens or spinners
- Empty: Helpful message with call-to-action
- Error: Recovery action, not just error text
- Success: Confirmation feedback
- Partial: Incomplete data handling
Design Principles
- Composition over inheritance: Small, composable components
- Controlled by default: Parent controls state via props
- Accessible first: Accessibility is not an afterthought
- Responsive by default: Mobile-first, progressive enhancement
- Performance-aware: Lazy loading, virtualization for large lists
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 · 109 lines · 222 tokens per session scan A 154232648408
designer is an agent published in the GitHub repository johnfkoo951/cmdspace-plugins (7 stars, last pushed today), licensed MIT. It adds 222 tokens to every session and 899 once invoked, about $0.0009 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
canvas-layout
Spatial positioning specialist for Obsidian Canvas. Computes optimal node positions using layout algorithms (dagre, grid, radial, force-directed, linear). Preserves zone containment, snaps to 20px grid, refits groups. Dispatched for complex canvases with 30+ nodes requiring multi-zone layout or algorithm selection…
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
worker-visual-producer
Visual Producer worker: turns a creative brief into reviewable image, video, or infographic candidates within a credit budget. Use when a page, post, product, or campaign needs original visuals: checks the brief, picks the model by task, drafts, looks at every output, refines the best, and stages candidates with…
pkm-capture
Use proactively in the background after completing significant work blocks, after git commits (triggered automatically by PreToolUse hook), or before session ends. Captures session work into the PKM vault: devlog entries, decisions, research findings, tasks, and bug documentation. Conservative — most exchanges produce…
vault-explorer
Use proactively when researching what the vault knows about a topic, before creating new notes, or when exploring existing knowledge and connections. Run in foreground — results inform the caller's next steps. Examples: Context: User asks about a topic before creating new content. user: "What does the vault already…