draft-reply

A Reddit reply drafting workflow that reads a specific thread, checks its subreddit rules, and runs the reply through a compliance check before posting.

In plain words
What is it for?
Use it to prepare a genuine, disclosed reply to a Reddit post or comment before publishing it.
Why use it?
It helps avoid writing replies that miss the discussion, break community rules, or create compliance problems. Posting still requires the user's explicit confirmation.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/lab2a/metalworks/draft-reply
Any agent
npx skills add Lab2A/metalworks --skill draft-reply
Clone the repo
git clone --depth 1 https://github.com/Lab2A/metalworks

Made for: Claude Code, Codex.

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 685 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00053 $0.00685
Opus 5 $0.00026 $0.00342
Sonnet 5 $0.00011 $0.00137
Haiku 4.5 $0.00005 $0.00068

Measured 2d ago against content hash 4000fd19c6c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

draft-reply 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 2d 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.

plugin/skills/draft-reply/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Preamble (run first)

Before any other tool, run the preflight MCP tool (or metalworks preflight on the CLI). If it reports setup issues or that an update is available, surface that to the user in one line and help them resolve it (install the missing extra/key, or pip install -U metalworks) before continuing. Skip only if the user has already passed preflight this session.

Read the reference; never reverse-engineer the source. The moment you need to know how metalworks behaves — provider/model resolution, which source/reader runs, config precedence, an error you hit, or the async run loop — STOP and read docs/operating-metalworks.md (bundled with this plugin) before opening any file under src/. It is the source of truth; do not derive behavior from source. (Full docs: https://metalworks.lab2a.ai/docs.) For a long-running run, poll status with the Monitor tool or a bounded loop — never a blind sleep.

You are drafting one genuine, disclosed Reddit reply for a thread the user provides, and gating it before anything is posted.

Steps

  1. Read the thread: call reddit_get_post_comments on the URL and reddit_subreddit_rules on its subreddit. Understand what the person is actually asking and what the subreddit allows.

  2. Draft a reply in the user's own voice. It must read as a real person sharing real experience: specific, helpful, no marketing tone, no calls to action, no em-dashes, no AI tells. If the user has an affiliation worth disclosing, disclose it plainly in the reply.

  3. Run the draft through compliance_lint. If it does not pass, revise and lint again. Loop until it passes. Show the user the violations you fixed.

  4. Present the final draft and the compliance verdict. Stop there. Do not post.

Posting (only on explicit confirmation)

Posting is a separate, deliberate action and is off by default. If, and only if, the user explicitly says to post it:

  • A passing compliance_lint returns a confirm_token over that exact text.
  • Posting also requires METALWORKS_ALLOW_POSTING=1 in the server environment and a connected Reddit account (metalworks reddit auth login).
  • Call reddit_post_comment with the URL, the exact drafted text, and that confirm_token. If the token does not match the text, or posting is not enabled, the tool refuses by design. Relay the refusal honestly.

Read the full file on GitHub · 59 lines

Changes

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.

  1. 2d ago First seen · 59 lines · 53 tokens per session scan A 4000fd19c6c2

Subscribe to this mod's changes

draft-reply is a skill published in the GitHub repository Lab2A/metalworks (6 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 685 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens