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 commands/volomydyr/design-engineer-plugin/stopgit clone --depth 1 https://github.com/volomydyr/design-engineer-pluginWhat 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.00044 | $0.00598 |
| Opus 5 | $0.00022 | $0.00299 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
design-engineer:stop 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 2d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stop and save progress
Spacer rule (per CLAUDE.md rule #6): Before every
AskUserQuestiontool call this command makes, end the preceding chat message with the canonical 3-horizontal-rule spacer (three lines of─characters).
What this command does
This is an optional safety net for pausing mid-activity. If you've completed a full activity (problem statement, assumptions, etc.), your progress is already saved automatically. Use /design-engineer:stop when you're in the middle of an activity and want to pause cleanly.
Step 1: Read current state
- Read
.design-engineer-plugin/config.yamlfor current phase, mode, and resume state - Read
.design-engineer-plugin/dependencies.yamlfor deliverable status - Check the current conversation for any in-progress work (partially drafted deliverables, unanswered questions, ongoing analysis)
Step 2: Save partial progress
If there is any in-progress work in the current conversation:
- Save whatever partial content exists to the appropriate deliverable file with a
[DRAFT – IN PROGRESS]marker at the top - Note what was completed and what remains in the file
If no in-progress work exists (the user just wants to stop between activities):
- Skip this step – automatic saving already handled it
Step 3: Update config
Update .design-engineer-plugin/config.yaml with the current resume state:
- Current phase and phase name
- Last completed skill
- Next skill (what to resume with)
- Timestamp
Step 4: Suggest compaction
Read skills/shared-references/compact-template.md and generate a ready-to-use compact message for the user. Present it:
"Your progress is saved. If you want to start a fresh session, here's a compact message you can use with
/compact:"[generated compact message]
Step 5: Confirm
Tell the user what was saved, where they are in the pipeline, and how to resume:
"Saved. You're in Phase [N] ([name]), last completed [skill]. Run
/design-engineer:launchin a new session to pick up where you left off."
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.
- 2d ago First seen · 70 lines · 44 tokens per session scan A d455068e9640
design-engineer:stop is a command published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 598 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.