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/robinsadeghpour/content-workflow/writingnpx skills add robinsadeghpour/content-workflow --skill writinggit clone --depth 1 https://github.com/robinsadeghpour/content-workflowWrote 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/robinsadeghpour/content-workflow/writing)<a href="https://agentmods.dev/skills/robinsadeghpour/content-workflow/writing"><img src="https://agentmods.dev/badge/skills/robinsadeghpour/content-workflow/writing.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.00120 | $0.02322 |
| Opus 5 | $0.00060 | $0.01161 |
| Sonnet 5 | $0.00024 | $0.00464 |
| Haiku 4.5 | $0.00012 | $0.00232 |
Grade A, and why
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 5d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing — Voice Profile and Humanizer Orchestration
Overview
This skill owns Robin's voice profiles and orchestrates the humanizer. Clean separation:
- Humanizer = removes AI patterns (generic — applies to any text)
- Writing skill = applies Robin's specific voice (platform-aware, identity-specific)
The humanizer runs first to strip generic AI patterns. The writing skill then applies Robin's actual fingerprint on top. This sequence matters — humanizer cleans the slate, writing skill adds the identity.
Voice profiles live in .claude/skills/writing/data/:
voice-linkedin.xml— LinkedIn formal-authentic profile (50 posts analyzed)voice-casual.xml— TikTok EN/DE + Instagram casual profile (50 posts analyzed)sample-posts-linkedin.md— Robin's actual LinkedIn posts (reference corpus)sample-posts-casual.md— Robin's actual X/casual posts (reference corpus)
Mode 1: Apply Voice to Draft (default)
Required argument: --platform linkedin|tiktok|instagram|tiktok_de
No implicit defaults. Platform must be explicit. Applying casual voice to LinkedIn or vice versa is a hard failure.
Workflow:
-
Read platform argument. Map to profile:
linkedin→.claude/skills/writing/data/voice-linkedin.xmltiktok,instagram,tiktok_de→.claude/skills/writing/data/voice-casual.xml
-
Read the target voice profile. Note the fingerprint, hook-patterns, and banned-patterns.
2b. Read the storytelling framework. Load .claude/skills/writing/data/storytelling-framework.md. Use it to evaluate draft structure:
- Does the draft follow Hook → Context → Tension → Pivot → Payoff progression?
- Does it address one person (not "hey guys")?
- Does it use "you" for desires and "I" for problems?
- Are there re-hooks or open loops to maintain attention? If the draft lacks structure, restructure it according to the 5-part framework before applying voice fingerprint.
- Receive the draft text (from user prompt or piped from another skill).
What ships with it
9 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.
- data/raw-lenny-posts.json 156 KB
- data/raw-linkedin-posts.json 226 KB
- data/raw-nick-saraev-posts.json 157 KB
- data/raw-x-posts.json 38 KB
- data/sample-posts-casual.md 8.5 KB
- data/sample-posts-linkedin.md 40 KB
- data/storytelling-framework.md 3.5 KB
- data/voice-casual.xml 7.0 KB
- data/voice-linkedin.xml 8.0 KB
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.
- 5d ago First seen · 183 lines · 120 tokens per session scan A b796a7180858
writing is a skill published in the GitHub repository robinsadeghpour/content-workflow (55 stars, last pushed 3mo ago), licensed MIT. It adds 120 tokens to every session and 2,322 once invoked, about $0.0006 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
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…