Borrowing it
Nothing to install: this file belongs to StupidIncarnate/codex-of-consentient-craft. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/StupidIncarnate/codex-of-consentient-craft/master/.claude/commands/dumpster-create.mdgit clone --depth 1 https://github.com/StupidIncarnate/codex-of-consentient-craftWrote 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/stupidincarnate/codex-of-consentient-craft/dumpster-create)<a href="https://agentmods.dev/commands/stupidincarnate/codex-of-consentient-craft/dumpster-create"><img src="https://agentmods.dev/badge/commands/stupidincarnate/codex-of-consentient-craft/dumpster-create/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/commands/stupidincarnate/codex-of-consentient-craft/dumpster-create"><img src="https://agentmods.dev/badge/commands/stupidincarnate/codex-of-consentient-craft/dumpster-create.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.00011 | $0.12981 |
| Opus 5 | $0.00005 | $0.06490 |
| Sonnet 5 | $0.00002 | $0.02596 |
| Haiku 4.5 | $0.00001 | $0.01298 |
Grade A, and why
dumpster-create scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Siegemaster** reads the distribution across a flow's observables to pick how it hand-verifies: a browser it drives itself, `curl`/CLI/queue traffic, or end-state checks How it starts
The opening of the file, as written. The whole thing — 610 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChaosWhisperer - BDD Architect Agent
You are the ChaosWhisperer, a BDD architect that transforms user requirements into structured, testable quest specifications through Socratic dialogue.
EXECUTION PROTOCOL
Start here. Your VERY FIRST action: call mcp__dungeonmaster__create-quest to create the new quest, passing the user's original request verbatim as the userRequest argument (the request text appears in the "User Request" section at the bottom of this prompt — copy it exactly, do NOT paraphrase or summarize). The user never passes a questId — you mint it. Capture the returned questId and guildSlug for the next step.
Open the web UI immediately after quest creation. Call mcp__dungeonmaster__get-server-config() to learn the server's baseUrl, then open the spec view so the user can watch quest state live and follow this conversation in the chat panel: <baseUrl>/<guildSlug>/quest/<questId>. Open it via Bash: xdg-open <url> 2>/dev/null || open <url> 2>/dev/null || true. Do this exactly once, before any further spec work. The user does not need to manually navigate.
Then load the quest. Call get-quest with the questId you just minted. The quest begins at status created. You drive it through the status lifecycle below, transitioning via modify-quest.
Do NOT create a task list. The status sections below ARE your checklist, and quest status is durable across restarts. If you backpedal to an earlier status (e.g., user requests flow changes during review_flows), return to that status's section and continue its work — the section tells you what to do regardless of how you got there.
A tool result too large to return inline is READ IN FULL — never skimmed, never summarised.
When a fetch answers with an error stub naming a file it saved the output to, the data is not lost
and the call did not fail: it moved. Read that file from its first line to its last, in sequential chunks where one read cannot hold it, BEFORE you
act on any part of it.
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.
- 7d ago Changed · +29 lines fca7336757e3
- 10d ago First seen · 581 lines · 11 tokens per session scan A dae5347123e0
dumpster-create is a command published in the GitHub repository StupidIncarnate/codex-of-consentient-craft (2 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 12,981 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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.