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 skills add robertguss/claude-code-toolkit --skill dhh-writinggit clone --depth 1 https://github.com/robertguss/claude-code-toolkitWrote 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/robertguss/claude-code-toolkit/dhh-writing)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/dhh-writing"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/dhh-writing/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.
<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/dhh-writing"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/dhh-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 162 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.1 | $0.00056 | $0.01457 |
| Opus 5.5 | $0.00022 | $0.00583 |
| Sonnet 5.5 | $0.00011 | $0.00291 |
| Haiku 4.5 | $0.00006 | $0.00146 |
Grade A, and why
dhh-writing 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 1mo 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DHH Writing Skill
Write in the distinctive style of David Heinemeier Hansson—direct, brave, opinionated prose that takes a stand and defends it unapologetically.
When to Use This Skill
This skill applies when:
- Writing opinion pieces or manifestos
- Creating blog posts that need to take a strong position
- Crafting business or product philosophy content
- Writing in a "Basecamp/37signals voice"
- Creating content that challenges conventional wisdom
- Any writing that needs to be punchy and memorable
Core Philosophy
"Strong opinions, weakly held" is half-right. You need strong opinions, strongly expressed. The weakness comes from being willing to change when presented with better evidence—not from hedging your delivery.
DHH's writing is characterized by:
- Conviction: Every piece has a clear position
- Courage: Willing to say unpopular things
- Clarity: No corporate-speak, no hedging
- Concision: Short sentences, short paragraphs
The 10 Core Techniques
Reference techniques.md for the complete guide.
1. Take a Stand
Every piece must have a thesis you can disagree with.
❌ "There are pros and cons to remote work that teams should consider."
✅ "Remote work is the future. Companies clinging to mandatory office time
will lose their best people to those who trust their employees."
2. No Hedging
Remove qualifiers that weaken your position.
Words to eliminate:
- "I think..." (just say it)
- "In my opinion..." (obviously)
- "It seems like..." (commit)
- "Some might say..." (who?)
- "Generally speaking..." (specifically speak)
3. Short Sentences
Punch. Impact. Clarity.
Long sentences with multiple clauses, while sometimes necessary for complex ideas that require careful qualification and nuanced expression, often dilute the force of your argument and lose readers who are scanning for the key point.
Short sentences work better.
They're memorable.
They're quotable.
They're true.
What ships with it
4 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.
- 1mo ago First seen · 208 lines · 56 tokens per session scan A a3a38ad5fba6
dhh-writing is a skill published in the GitHub repository robertguss/claude-code-toolkit (127 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,457 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-edr-evasion
EDR evasion offensive checklist: hook unhooking (user/kernel), direct syscalls, PPID spoofing, process injection variants, AMSI bypass, ETW patching, memory encryption, and behavior-based evasion. Use when planning EDR bypass during red team engagements or researching AV/EDR evasion techniques.
offensive-initial-access
Initial access techniques checklist: phishing (spear/smishing), credential stuffing, exposed service exploitation, supply chain attacks, watering hole, VPN/RDP brute force, public-facing application exploitation. Maps to MITRE ATT&CK TA0001. Use when planning initial access phases of red team engagements.
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-k8s-attacks
Kubernetes cluster attack techniques covering the full attack lifecycle from initial foothold in a pod to cluster-wide compromise. Covers service account token theft and impersonation, RBAC misconfiguration exploitation including wildcard permissions and privilege escalation via role binding, direct etcd access for…
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.