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 writing-dna-discoverygit 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/writing-dna-discovery)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/writing-dna-discovery"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/writing-dna-discovery.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.1 | $0.00066 | $0.03054 |
| Opus 5 | $0.00033 | $0.01527 |
| Sonnet 5 | $0.00013 | $0.00611 |
| Haiku 4.5 | $0.00007 | $0.00305 |
Grade A, and why
writing-dna-discovery 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 7d 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing DNA Discovery
Capture the genetic code of a writer's voice through collaborative interview and sample analysis.
Core Philosophy
This is genuine intellectual partnership, not interrogation or extraction:
- Contribute substance — Offer observations, pattern recognition, and insights proactively. Don't just ask questions; bring analysis to the table.
- Push back with reasoning — Challenge vague answers, but always explain WHY. "That description could apply to many writers—what makes YOUR voice specifically recognizable?"
- One question at a time — Never overwhelm with multiple questions. One focused question per response.
- The human is the expert — They know their voice better than any analysis can capture. Your job is to help them articulate and document it.
- Surface problems early — If something contradicts or doesn't fit, say so. A flawed DNA document produces flawed ghost writing.
What This Skill Does
- Analyzes writing samples for distinctive patterns
- Conducts collaborative interview to surface choices and preferences
- Documents voice dimensions with examples
- Produces actionable Voice DNA Document for ghost writer skill
- Supports refinement and evolution over time
Key Design Principles
One Register Per Session Focus on a single mode: fiction prose, blog posts, technical writing, etc. Each register may have different voice characteristics. The user can create multiple DNA documents for different registers.
80% Approximation Goal The DNA document enables a ghost writer to produce first drafts at ~80% accuracy. The human adds the remaining 20%—the creative spark, situational judgment, and final polish. We're not replacing the writer; we're giving them a strong starting point.
Living Document The Voice DNA Document grows richer over time. Initial sessions capture the foundation; return sessions deepen, refine, and adapt as the writer's voice evolves.
Comprehensive Capability, Intelligent Application This skill has a full arsenal of voice dimensions but deploys them thoughtfully. Don't march through every dimension mechanically. Focus on what's most distinctive and relevant for this writer and register.
What ships with it
7 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.
- 7d ago First seen · 385 lines · 66 tokens per session scan A 4cb49c79d2a1
writing-dna-discovery is a skill published in the GitHub repository robertguss/claude-code-toolkit (113 stars, last pushed 29d ago), licensed MIT. It adds 66 tokens to every session and 3,054 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-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-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-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.
offensive-tls-attacks
Comprehensive methodology for auditing and exploiting TLS/SSL implementations and misconfigurations across network services and mobile applications. Covers protocol downgrade attacks including POODLE (CVE-2014-3566) against SSLv3 CBC padding, DROWN (CVE-2016-0800) cross-protocol attack leveraging SSLv2 export ciphers…
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…