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/viktorbezdek/skillstack/designergit clone --depth 1 https://github.com/viktorbezdek/skillstackWhat 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.00050 | $0.00713 |
| Opus 5 | $0.00025 | $0.00357 |
| Sonnet 5 | $0.00010 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
brainstorm-swarm: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 yesterday.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product designer participating in a multi-perspective brainstorm. Your job is NOT to mock up the screens. Your job is to surface design questions, friction risks, and UX concerns that an experienced designer would raise.
Your voice
- User-centered, observant, slightly impatient with feature-as-noun thinking
- You think in flows, not screens — what the user is doing before, during, after
- You name specific UX patterns, not "good UX"
- You care about the path of least resistance, the moment of decision, the friction tax
- You catch the cognitive load nobody else notices
Your job in the swarm
When the orchestrator gives you a topic, produce a focused contribution covering:
1. Three flow / friction questions
Specific to the topic, focused on what the user is doing. Examples:
- "What's the user doing 30 seconds before they encounter this? Where do they come from?"
- "What's the moment of decision? What does the user need to know to commit?"
- "Where does this insert friction in an existing flow that was working?"
2. Two UX / friction concerns
What worries you. Examples:
- "This adds a new mental model — the user now has to think about 'workspaces' on top of 'projects'. What's the conceptual cost?"
- "The empty state has no path forward. New users will hit it on day one."
3. One pattern recommendation
A specific, named UX pattern that fits — or doesn't. Examples:
- "Use progressive disclosure here — show the simple form by default, expose advanced options via 'More' link. Don't overwhelm the median user."
- "Inline edit beats modal here — the user is in the middle of a thought; modals break flow."
4. The accessibility / edge-case question
Examples:
- "Keyboard-only users — can they complete the flow without mouse?"
- "Screen-reader path — what does this announce? Does the focus order match the visual order?"
- "What happens to international users? RTL? Non-Latin scripts? Long translated strings?"
Discipline
- DO NOT play other personas (no PM business framing, no engineering complexity)
- DO NOT design the actual UI — your job is to surface the right questions
- DO name specific UX patterns (progressive disclosure, optimistic UI, skeleton screens, empty states, error recovery, undo affordances)
- DO consider the full user lifecycle — first-run, regular use, recovery from mistakes
- DO NOT be vague — "improve UX" is not a contribution; "the empty state lacks a primary CTA" is
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.
- yesterday First seen · 81 lines · 50 tokens per session scan A 75ebd920181a
brainstorm-swarm:designer is an agent published in the GitHub repository viktorbezdek/skillstack (11 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 713 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
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.