dead-drop-responder

dead-drop-responder is a skill for Claude Code, Codex from drscotthawley/slmn. It costs 80 tokens per session (717 once invoked), scanned A, original, Apache-2.0.

Um agente que responde a mensagens trocadas por ficheiros numa pasta chamada dead drop, um canal simples de comunicação entre programas.

In plain words
What is it for?
Serve para vigiar novos pedidos, ler o contexto de cada mensagem e gravar a resposta no ficheiro correspondente.
Why use it?
Permite responder a pedidos recebidos sem uma ligação direta entre o programa que pergunta e o modelo que responde.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Serve para vigiar novos pedidos, ler o contexto de cada mensagem e gravar a resposta no ficheiro correspondente.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/drscotthawley/slmn/dead-drop-responder
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.

Any agent
npx skills add drscotthawley/slmn --skill dead-drop-responder
Clone the repo
git clone --depth 1 https://github.com/drscotthawley/slmn

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for dead-drop-responder

README.md
[![agentmods](https://agentmods.dev/badge/skills/drscotthawley/slmn/dead-drop-responder/github.svg)](https://agentmods.dev/skills/drscotthawley/slmn/dead-drop-responder)
Your own site
<a href="https://agentmods.dev/skills/drscotthawley/slmn/dead-drop-responder"><img src="https://agentmods.dev/badge/skills/drscotthawley/slmn/dead-drop-responder/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.

agentmods 80×15 button for dead-drop-responder

Your own site · 80×15
<a href="https://agentmods.dev/skills/drscotthawley/slmn/dead-drop-responder"><img src="https://agentmods.dev/badge/skills/drscotthawley/slmn/dead-drop-responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 717 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00080 $0.00717
Opus 5 $0.00040 $0.00358
Sonnet 5 $0.00016 $0.00143
Haiku 4.5 $0.00008 $0.00072

Measured 12d ago against content hash c4773b198081, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

dead-drop-responder 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 12d 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.

slmn/skills/dead-drop-responder/SKILL.md · 58 lines

How it starts

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

Dead-drop responder

You are the model on the far side of a file-based prompt/response exchange (see slmn.dead_drop). A producer -- typically a boopiter notebook with the deaddrop/claude model selected -- drops each prompt as a file in ~/dead_drop/prompts/; you answer by writing ~/dead_drop/responses/<same-name>.

The loop

  1. Arm the watch (run as a background command; its exit is your wake-up call):

    slmn watch_prompts
    

    It blocks until a prompt lands, prints it as one JSON line ({"name": ..., "content": ...}), consumes the prompt file, and exits.

  2. When it fires: read the JSON from the task output. Compose your reply to content (it is the notebook's full visible context; the [system: ...] trailer about ---MODEL: is instructions for you, not part of the question).

  3. Reply (body via stdin spares shell-quoting; name is from step 1's JSON):

    slmn respond_prompt <name> --model "<your model name and version>" <<'EOF'
    ...your reply in markdown...
    EOF
    

    respond_prompt appends the ---MODEL: ...--- line and ---DONE--- terminator itself -- do not include them in the body.

  4. Re-arm (slmn watch_prompts again, in the background) so the next prompt is caught. Repeat until told to stop.

Rules that keep it friction-free

  • Run every slmn command ALONE in its shell call. Permission allowlists match the whole command line: slmn ... && git status, a (cd ...) subshell, or any appended command breaks the match and triggers a permission prompt.
  • Don't poll for the watch result -- the background task's exit notifies you.
  • If a prompt references images as ![...](/boopimg/<hex>.png), only the tag reaches you as text. If you are on the producer's machine, the file lives at <boopiter-launch-dir>/.boopiter/images/<hex>.png -- read it and answer about the actual image; otherwise say you received only the reference.
  • One response file per prompt name, exactly. If the same context arrives twice under two names (e.g. the user double-ran the cell), answer each name -- the notebook only follows the newest.

Read the full file on GitHub · 58 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. 12d ago First seen · 58 lines · 80 tokens per session scan A c4773b198081

Subscribe to this mod's changes

dead-drop-responder is a skill published in the GitHub repository drscotthawley/slmn (1 stars, last pushed 26d ago), licensed Apache-2.0. It adds 80 tokens to every session and 717 once invoked, about $0.0004 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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens