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/tidygit clone --depth 1 https://github.com/volomydyr/design-engineer-pluginWrote 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/commands/volomydyr/design-engineer-plugin/tidy)<a href="https://agentmods.dev/commands/volomydyr/design-engineer-plugin/tidy"><img src="https://agentmods.dev/badge/commands/volomydyr/design-engineer-plugin/tidy.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.01055 |
| Opus 5 | $0.00016 | $0.00528 |
| Sonnet 5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
design-engineer:tidy 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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tidy disposable working artifacts
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).
Plugin paths
Your conversation context contains a line DESIGN_ENGINEER_PLUGIN_ROOT: <absolute path> injected by the plugin's UserPromptSubmit hook. Whenever this command references ${DESIGN_ENGINEER_PLUGIN_ROOT}/..., substitute the absolute path from that context line. No shell commands are run from this command body.
What this command does
The plugin keeps disposable working artifacts (Playwright debug captures, intermediate analysis dumps, exploratory drafts) under .design-engineer-plugin/temporary/. That directory is git-ignored and auto-purged at every phase boundary by /design-engineer:document. This command does the same purge on demand — useful before a commit, or anytime the working tree feels noisy.
The command never touches durable deliverables (design/, prototype/, plans/, memory/). It only wipes temporary/.
Step 0: Verify this is a plugin project
Run via Bash:
test -f .design-engineer-plugin/config.yaml && echo "OK" || echo "NO_CONFIG"
If the output is NO_CONFIG, exit immediately with the message:
This isn't a design-engineer plugin project. Run
/design-engineer:launchfirst to set one up.
Step 1: Count and summarize what will be purged
Run via Bash:
bash -c '
TEMP_DIR=".design-engineer-plugin/temporary"
if [ ! -d "$TEMP_DIR" ]; then
echo "EMPTY"
exit 0
fi
FILE_COUNT=$(find "$TEMP_DIR" -mindepth 1 -type f 2>/dev/null | wc -l | tr -d " ")
DIR_COUNT=$(find "$TEMP_DIR" -mindepth 1 -type d 2>/dev/null | wc -l | tr -d " ")
TOTAL_SIZE=$(du -sh "$TEMP_DIR" 2>/dev/null | cut -f1)
echo "FILES=$FILE_COUNT DIRS=$DIR_COUNT SIZE=$TOTAL_SIZE"
'
Parse the output. If EMPTY or FILES=0, surface to the user:
.design-engineer-plugin/temporary/is already empty. Nothing to tidy.
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.
- 4d ago First seen · 95 lines · 33 tokens per session scan A beb88c6f723d
design-engineer:tidy is a command published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,055 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.