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 skills/douglance/sdlc-plugin/actionable-communicationnpx skills add douglance/sdlc-plugin --skill actionable-communicationgit clone --depth 1 https://github.com/douglance/sdlc-pluginWrote 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/skills/douglance/sdlc-plugin/actionable-communication)<a href="https://agentmods.dev/skills/douglance/sdlc-plugin/actionable-communication"><img src="https://agentmods.dev/badge/skills/douglance/sdlc-plugin/actionable-communication.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.00034 | $0.00608 |
| Opus 5 | $0.00017 | $0.00304 |
| Sonnet 5 | $0.00007 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
actionable-communication 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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Actionable Communication
Turn consequential communication into a compact control surface for its reader. Preserve technical truth; change only how it is prioritized and handed off. Routine conversation follows the host's lightweight communication rules without loading this skill.
Messaging standards
Load the UWDS reference when producing or reviewing formal documentation, requirements, procedures, interface content, safety or accessibility content, or when a scoped standards question arises. For a simple status, blocker, or handoff, use the compact rules below without loading the reference.
The reference is references/unified-writing-documentation-standard.md. Treat it as the canonical Markdown communication baseline without claiming blanket conformance to an external standard.
Resolve conflicts in UWDS precedence order: binding authority; safety or domain standard; project terminology and product specification; audience and platform conventions; UWDS; then general house style. Use AP style only for news, press releases, and public announcements; do not use it as the default for engineering artifacts or technical procedures.
Write in decision order
- Lead with the outcome, blocker, or decision needed.
- State the lifecycle phase and whether it completed, partially completed, or stopped.
- Give the evidence that makes the status credible: artifacts, commands, results, or exact failure.
- List unresolved items only when they affect acceptance or the next phase.
- Name one next action only when someone must act. Name its owner when known.
For multi-step work, use a numbered list with no more than five immediate items. Keep later possibilities out of the immediate-action list.
Make failures actionable
Report an error as:
- Cause: the narrowest supported explanation.
- Evidence: the observation, command, or artifact that supports it.
- Remedy: the smallest next test or change likely to unblock progress.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 57 lines · 34 tokens per session scan A 9a352c478b41
actionable-communication is a skill published in the GitHub repository douglance/sdlc-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 608 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…