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/cost-modegit 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/cost-mode)<a href="https://agentmods.dev/commands/volomydyr/design-engineer-plugin/cost-mode"><img src="https://agentmods.dev/badge/commands/volomydyr/design-engineer-plugin/cost-mode.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.00036 | $0.00917 |
| Opus 5 | $0.00018 | $0.00458 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
design-engineer:cost-mode 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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Engineer – Cost mode
Plugin paths
Your conversation context contains a line DESIGN_ENGINEER_PLUGIN_ROOT: <absolute path> injected by the plugin's UserPromptSubmit hook. Whenever this command body references ${DESIGN_ENGINEER_PLUGIN_ROOT}/..., substitute the absolute path from that context line.
Context
#$ARGUMENTS
Step 1: Parse the argument
Read $ARGUMENTS. It must be exactly light or full. If anything else (empty, lite, medium, etc.), end the preceding chat message with the canonical 3-horizontal-rule spacer (per CLAUDE.md rule #6) and call AskUserQuestion:
question: "Which mode do you want to switch to?"
header: "Plugin mode"
options:
- label: "Light"
description: "Faster, lower token cost. All AI components run on Sonnet at medium effort. No Opus anywhere. Recommended if you have a usage limit or run long sessions."
- label: "Full"
description: "Higher quality. Most components run on Opus at high effort; some lighter-weight transforms (setup wizards, documentation, structured outputs) run on Sonnet. Higher token cost per session. Recommended when usage isn't a constraint."
multiSelect: false
Use the user's answer (light or full) as the target mode.
Step 2: Update the project config
Run via Bash:
mkdir -p .design-engineer-plugin
CONFIG=".design-engineer-plugin/config.yaml"
if [ -f "$CONFIG" ]; then
if grep -qE '^cost_mode:' "$CONFIG"; then
# Replace existing line
sed -i.tmp -E "s/^cost_mode:.*/cost_mode: <MODE>/" "$CONFIG"
rm "$CONFIG.tmp"
else
# Append
printf '\ncost_mode: <MODE>\n' >> "$CONFIG"
fi
else
printf 'cost_mode: <MODE>\n' > "$CONFIG"
fi
Replace <MODE> with the target mode from Step 1.
Step 3: Apply the rewrite
Run the apply script via Bash, passing ${CLAUDE_PLUGIN_ROOT} resolved from the context line at the top of this file:
CLAUDE_PLUGIN_ROOT="${DESIGN_ENGINEER_PLUGIN_ROOT}" bash "${DESIGN_ENGINEER_PLUGIN_ROOT}/scripts/apply-cost-mode.sh"
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.
- 5d ago First seen · 83 lines · 36 tokens per session scan A 1c5a80e90dea
design-engineer:cost-mode is a command published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 917 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.