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/paultyng/agentsd/claude-mdgit clone --depth 1 https://github.com/paultyng/agentsdWrote 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/paultyng/agentsd/claude-md)<a href="https://agentmods.dev/instructions/paultyng/agentsd/claude-md"><img src="https://agentmods.dev/badge/instructions/paultyng/agentsd/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.00447 | $0.00447 |
| Opus 5 | $0.00224 | $0.00224 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade B, and why
agentsd CLAUDE.md scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `npm run hooks:install` / `npm run hooks:uninstall` — manage Claude Code HTTP hooks in `~/.claude/settings.json` What it actually says
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project
agentsd — a Stream Deck plugin for orchestrating local AI agent usage. Early stages.
Build & Test
Use npm scripts only — no Taskfile or Makefile.
npm run build— rollup build →com.paultyng.agentsd.sdPlugin/bin/plugin.jsnpm run watch— rollup watch modenpm run dev— Stream Deck dev modenpm run link/npm run unlink— link/unlink plugin in Stream Decknpm run hooks:install/npm run hooks:uninstall— manage Claude Code HTTP hooks in~/.claude/settings.jsonnpm run debug:hooks— interactive hook debug script
Architecture
Claude Code HTTP hooks → Plugin HTTP server (127.0.0.1:9200) → SessionManager → Stream Deck button/dial updates. No bridge daemon, no PTY parsing. PermissionRequest hooks hold HTTP response open (120s timeout) for approve/deny from hardware buttons.
State machine
Sessions move through 5 states: DISCONNECTED → IDLE → PROCESSING → AWAITING_PERMISSION / AWAITING_ELICITATION.
Auto-created sessions (missed SessionStart) start as IDLE. Current-state guards prevent nonsensical transitions (e.g. tool events from DISCONNECTED).
PostToolUse intentionally stays in PROCESSING — Stop moves to IDLE.
Key behaviors
- Auto-foreground: Elicitation and PermissionRequest events bring the session to the active slot.
- Stale pruning: Sessions with no activity for 60s are pruned (PRUNE_INTERVAL_MS = 60s check).
- Permission timeout: 120s (PERMISSION_TIMEOUT_MS). Sends explicit deny on timeout.
- Action DI pattern: A single
setManager()call inplugin.tswires theSessionManagerinto allManagedActionsubclasses via a shared module-level reference inactions/base.ts.
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 · 37 lines · 447 tokens per session scan B b8f0439f0add
agentsd CLAUDE.md is an instructions file published in the GitHub repository paultyng/agentsd (10 stars, last pushed 22d ago), licensed MIT. It adds 447 tokens to every session, about $0.0022 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
OpenDeck AGENTS.md
AGENTS.md instructions for nekename/OpenDeck, covering opendeck development guide, token efficiency, architecture overview, core architecture pattern and project structure.
streamdeck-mcp CLAUDE.md
Instructions for verygoodplugins/streamdeck-mcp, covering claude.md, development commands, setup, run server (for claude desktop) and lint.
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.
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.