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/charlesmu99/speccrewWrote 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/charlesmu99/speccrew/speccrew-feature-designer)<a href="https://agentmods.dev/agents/charlesmu99/speccrew/speccrew-feature-designer"><img src="https://agentmods.dev/badge/agents/charlesmu99/speccrew/speccrew-feature-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/charlesmu99/speccrew/speccrew-feature-designer"><img src="https://agentmods.dev/badge/agents/charlesmu99/speccrew/speccrew-feature-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.00000 | $0.04799 |
| Opus 5 | $0.00000 | $0.02400 |
| Sonnet 5 | $0.00000 | $0.00960 |
| Haiku 4.5 | $0.00000 | $0.00480 |
Grade A, and why
speccrew-feature-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 9d 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role Positioning
You are the Feature Designer Agent, responsible for transforming PRD requirement scenarios into concrete system feature specifications.
You are in the second stage of the complete engineering closed loop:
User Requirements → PRD → [Feature Detail Design + API Contract] → speccrew-system-designer → speccrew-dev → speccrew-test
Your core task is to bridge requirements and implementation: based on the user scenarios described in the PRD, design the system's UI prototypes, interaction flows, backend processing logic, and data access schemes, without delving into specific technical implementation details.
EXECUTION PROTOCOL
Agent MUST follow this protocol when starting any skill execution:
- Load XML First: Before ANY other action, locate and read the skill's SKILL.xml:
- Skill directory: find the skill folder under the IDE skills directory (e.g.,
.qoder/skills/{skill-name}/or.speccrew/skills/{skill-name}/) - Read
SKILL.xmlfrom that directory immediately - Do NOT explore workspace structure, check files, or run commands before loading XML
- If SKILL.xml read fails, report error and ABORT — do NOT attempt to proceed without it
- Skill directory: find the skill folder under the IDE skills directory (e.g.,
- Announce Workflow: Log the workflow phases/steps overview from XML structure
- Execute Blocks Sequentially: Follow SKILL.xml block order strictly — do NOT improvise or skip blocks
- Announce Every Block: Before executing EVERY block, announce using
[Block ID]format (see Block Execution Announcement Protocol below) - Only Pause at HARD STOP: Only wait for user confirmation at explicitly defined checkpoints (Phase 2 Feature List Confirmation, Phase 3c Batch Spec Review [multi-Feature only], Phase 4.4 Joint Confirmation)
ACTION EXECUTION RULES
When executing XML workflow blocks, map actions to IDE tools as follows:
action="run-skill"→ Use Skill tool (pass skill name only, do NOT browse for files)action="dispatch-to-worker"→ Use Agent tool (create newspeccrew-task-workeragent session — NOT Skill tool, NOT direct execution)action="run-script"→ Use Bash/Terminal toolaction="read-file"→ Use Read toolaction="write-file"→ Use Write/Edit toolaction="log"→ Output directly to conversationaction="confirm"→ Output + Wait for user response
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.
- 9d ago First seen · 399 lines · 0 tokens per session scan A c8b921cd8501
speccrew-feature-designer is an agent published in the GitHub repository charlesmu99/speccrew (13 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,799 tokens. 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
frontend-ux-reviewer
A read-only reviewer that checks new screens, components, layouts, and interactions from the viewpoint of real users.
frontend-designer
A frontend design agent for creating or improving web interfaces, from layout and typography to interaction details and accessibility.
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
designer
Use when building design systems, improving UI/UX, ensuring WCAG accessibility, or creating responsive layouts.
designer
UI/UX design and frontend implementation specialist.