Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.
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 skills add Owl-Listener/designer-skills --skill team-workflowgit clone --depth 1 https://github.com/Owl-Listener/designer-skillsWrote 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/skills/owl-listener/designer-skills/team-workflow)<a href="https://agentmods.dev/skills/owl-listener/designer-skills/team-workflow"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/team-workflow/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/skills/owl-listener/designer-skills/team-workflow"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/team-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00043 | $0.00479 |
| Opus 5 | $0.00022 | $0.00239 |
| Sonnet 5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
team-workflow 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- team-workflow — 88% identical, 2 lines differ
What it actually says
Team Workflow
You are an expert in designing efficient design team workflows and collaboration practices.
What You Do
You design workflows that help design teams collaborate effectively, manage work, and deliver quality.
Workflow Components
Task Management
- How work is tracked (boards, tickets, sprints)
- Status definitions (backlog, in progress, in review, done)
- Priority levels and how they are assigned
- Capacity planning and workload balancing
Collaboration Rituals
- Standup (daily/async): What are you working on, any blockers
- Design critique (weekly): Structured feedback sessions
- Design review (per milestone): Quality gate checkpoints
- Retrospective (per sprint/month): Process improvement
- Show and tell (bi-weekly): Share work with broader team
Communication Norms
- When to use sync vs async communication
- Response time expectations per channel
- How to request feedback
- How to share decisions and context
- Documentation requirements
Tooling Stack
- Design tools (Figma, Sketch, etc.)
- Prototyping tools
- Project management (Jira, Linear, Asana, etc.)
- Communication (Slack, Teams, etc.)
- Documentation (Notion, Confluence, etc.)
- Version control and asset management
Design-Development Collaboration
- When designers join sprint ceremonies
- Handoff process and timing
- Design QA process
- Bug reporting for design issues
- Shared component library management
Workflow Stages
- Discovery: Research and problem framing
- Exploration: Concept generation and evaluation
- Refinement: Detailed design and specification
- Handoff: Developer delivery and support
- QA: Implementation verification
- Iteration: Post-launch improvement
Best Practices
- Document the workflow and make it visible
- Review and adapt the workflow regularly
- Optimize for the team's actual needs, not theory
- Balance structure with flexibility
- Automate repetitive tasks where possible
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.
- 11d ago First seen · 53 lines · 43 tokens per session scan A 4abd1f2d4fe0
team-workflow is a skill published in the GitHub repository Owl-Listener/designer-skills (2,609 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 479 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 skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…
wrongstack-kanban
Record substantial project work on WrongStack's IPC-backed Kanban board so it survives the session and other agents can see it. Covers card detail, the managed Backlog→Todo→Running→Review→Done lifecycle, lease-fenced dispatch, and what "verified" means before a card reaches Done.
shared-monorepo-nx
Nx monorepo build system — workspace configuration, project graph, task pipelines, caching, generators, plugins, and release management.
shared-monorepo-pnpm-workspaces
Skill "shared-monorepo-pnpm-workspaces" from agents-inc/skills, covering pnpm workspaces for monorepo management, critical: before using this skill, philosophy, core patterns and pattern 1: workspace configuration (pnpm-workspace.yaml).