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 instructions/volomydyr/design-engineer-plugin/claude-mdgit 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/instructions/volomydyr/design-engineer-plugin/claude-md)<a href="https://agentmods.dev/instructions/volomydyr/design-engineer-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/volomydyr/design-engineer-plugin/claude-md.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.17303 | $0.17303 |
| Opus 5 | $0.08651 | $0.08651 |
| Sonnet 5 | $0.03461 | $0.03461 |
| Haiku 4.5 | $0.01730 | $0.01730 |
Grade D, and why
design-engineer-plugin CLAUDE.md scanned grade D with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Debugging**: run `tail -f ~/.claude/cache/de-process-recall.log` to verify the hook fires when expected. Each fire appends a single line of the form `[ISO_TIMESTAMP] FIRED | workflow=<name> cwd=<path>`. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
The default `<YYYY-MM-DD-HHMMSS>` timestamp pattern for scratch captures keeps debug output organized by session — easy to scan, easy to delete a day's worth in one `rm -rf .design-engineer-plugin/temporary/playwright/20 How it starts
The opening of the file, as written. The whole thing — 945 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Engineer Plugin Development
Skill loading from commands (doc-compliant pattern)
This plugin's skills all set disable-model-invocation: true (intentional — skills are libraries loaded by commands, not auto-discoverable workflows). The Skill tool will REJECT any attempt to invoke them programmatically with the error: Skill <name> cannot be used with Skill tool due to disable-model-invocation.
Therefore, never tell the model to "load the X skill" or "invoke the Y skill" in a command body. The model interprets that as a Skill-tool call and the command crashes on the very first run.
The required pattern
Every command file MUST start its body with this short note (placed just after the # Title heading and before any other section):
## 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.
This relies on a single, permission-free mechanism: the plugin's UserPromptSubmit hook (hooks/de-start-state.sh) injects DESIGN_ENGINEER_PLUGIN_ROOT: <abs path> as additionalContext text on every prompt. The model sees that line in its context and uses it as the substitution value when it encounters ${DESIGN_ENGINEER_PLUGIN_ROOT}/... in the command body.
Mechanisms NOT to use, and why
- Bash injection (
!`...`) — documented at https://code.claude.com/docs/en/slash-commands.md#inject-dynamic-context, but Claude Code's permission system blocks!-prefix patterns at command-load time in Auto mode and any restrictive permission preset, with:Shell command permission check failed for pattern "!...". Permission for this action has been denied. Reason: Insufficient information about the Bash command to evaluate; action is unverifiable.v4.8.5 tried this approach and crashed/design-engineer:launchfor users in Auto mode. Do NOT use bash injection in command bodies. ${CLAUDE_PLUGIN_ROOT}— officially documented forhooks/hooks.jsoncommandfields ONLY. Does not auto-expand inside slash command markdown bodies. Hooks may use it; commands may not.Skilltool to invoke plugin skills — every plugin skill setsdisable-model-invocation: true, so the Skill tool will reject them withSkill <name> cannot be used with Skill tool due to disable-model-invocation. The only correct way to load a skill isRead ${DESIGN_ENGINEER_PLUGIN_ROOT}/skills/<name>/SKILL.md and follow its instructions inline.
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 · 945 lines · 17,303 tokens per session scan D 8d14d9fa9d92
design-engineer-plugin CLAUDE.md is an instructions file published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 2mo ago), licensed MIT. It adds 17,303 tokens to every session, about $0.0865 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.