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/claude-dev-suite/claude-dev-suite/community-draftgit clone --depth 1 https://github.com/claude-dev-suite/claude-dev-suiteWrote 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/claude-dev-suite/claude-dev-suite/community-draft)<a href="https://agentmods.dev/commands/claude-dev-suite/claude-dev-suite/community-draft"><img src="https://agentmods.dev/badge/commands/claude-dev-suite/claude-dev-suite/community-draft.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.00023 | $0.00752 |
| Opus 5 | $0.00012 | $0.00376 |
| Sonnet 5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
community-draft 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Draft
Draft an authentic, helpful reply for a community discussion about Claude Code, MCP servers, or AI-assisted development — mentioning dev-suite naturally where it's genuinely relevant.
How to execute this command
-
Identify the source:
- If
$ARGUMENTScontains a URL, use it as context - If
$ARGUMENTScontains pasted text, use it directly - If no arguments, ask the user to paste the discussion content
- If
-
Detect the platform from the URL or context:
github.com→ GitHub issue or discussionreddit.com→ Reddit post/commentnews.ycombinator.com→ HN threaddev.to→ dev.to article commentdiscord→ Discord message- Unknown → Ask the user
-
Read the discussion carefully and determine:
- What is the user's actual problem or question?
- Is dev-suite genuinely helpful here, or would mentioning it be spam?
- What's the most useful thing to say regardless of dev-suite?
-
Draft the reply following platform-specific tone:
Platform Tone Guidelines
GitHub Issues / Discussions
- Technical, direct, helpful
- Answer the question first, mention dev-suite only if it directly solves their problem
- Include code examples or config snippets when relevant
- Sign off with "— Mario, dev-suite author" only if dev-suite is mentioned
Hacker News
- No markdown (plain text only)
- Conversational but substantive
- Acknowledge counterpoints
- Never start with "Great question!" or sycophantic phrases
- Mention dev-suite only if directly asked or obviously relevant
- Match subreddit culture (r/ClaudeAI is casual, r/programming is technical)
- First paragraph: answer the question without self-promotion
- Second paragraph (only if relevant): "I built dev-suite which addresses this — [specific feature]"
- No link unless specifically helpful
dev.to / Hashnode
- Friendly, encouraging tone
- Can be slightly longer
- Link to relevant documentation or the repo if directly relevant
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 · 104 lines · 23 tokens per session scan A 2b7464e10a00
community-draft is a command published in the GitHub repository claude-dev-suite/claude-dev-suite (30 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 752 once invoked, about $0.0001 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
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Sync
Sync delta specs from a change to main specs.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
standards
Retrieve auto-detected coding standards and patterns from this project.