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 ericrisco/rsc-harness --skill article-writinggit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/article-writing)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/article-writing"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/article-writing.svg" alt="Measured on agentmods" 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 Prompt Injection · line 49 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00087 | $0.02790 |
| Opus 5 | $0.00044 | $0.01395 |
| Sonnet 5 | $0.00017 | $0.00558 |
| Haiku 4.5 | $0.00009 | $0.00279 |
Grade A, and why
article-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 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Article writing
Draft one long-form article end to end: the prose and the on-page surface that ships with it — answer-first lede, question-shaped headings, title tag, meta description, slug, FAQ block, and the JSON-LD that makes the piece machine-readable.
You own a single finished article. You do not pick the topic, build the calendar, or define the house voice — those are siblings below.
When NOT to use
| You want… | Go to |
|---|---|
| Keyword research, SERP tracking, technical SEO, deciding which topics to target | ../seo-geo/SKILL.md |
| Editorial calendar, topic-cluster plan, pipeline across many pieces | ../content-engine/SKILL.md |
| The reusable brand tone-of-voice spec the article is written in | ../brand-voice/SKILL.md |
| A conversion landing or sales page (hero, offer, CTA) | ../landing-copy/SKILL.md |
| An email newsletter issue (subject line, send) | ../newsletter/SKILL.md |
| Product docs, API reference, software how-tos | ../technical-writing/SKILL.md |
| A customer outcome story / narrative | ../case-studies/SKILL.md |
Rule: if the deliverable is not one publishable article, you are in the wrong skill.
Start from intent, not a word count
Before you write a sentence, read the top of the SERP for the target query. Name two things: the dominant intent (informational, transactional, comparison, navigational) and the winning format Google already rewards (listicle, step guide, definition + table, comparison). Match that format — fighting the shape Google already chose loses.
Then set depth from intent, not from a number you were handed. The first-page Google average is ~1,447 words across 11.8M results (Backlinko) — a descriptive average, never a target. Thoroughness and intent satisfaction rank, not length.
| Intent | Typical depth | Shape |
|---|---|---|
| Simple how-to / quick answer | 400–800 words | Direct answer, short steps, one image |
| Standard informational post | 1,500–2,000 words | Answer-first lede + question H2s |
| Comprehensive guide | 1,700–2,500 words | Full subtopic coverage, tables, FAQ |
| Pillar page | 2,500–5,000 words | Hub with two-way cluster links |
What ships with it
5 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 · 159 lines · 87 tokens per session scan A b4886069d488
article-writing is a skill published in the GitHub repository ericrisco/rsc-harness (70 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 2,790 once invoked, about $0.0004 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
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
setting-up-a-project
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
detecting-process-injection-techniques
Detects and analyzes process injection techniques used by malware including classic DLL injection, process hollowing, APC injection, thread hijacking, and reflective loading. Uses memory forensics, API monitoring, and behavioral analysis to identify injection artifacts. Activates for requests involving process…
extracting-iocs-from-malware-samples
Extracts indicators of compromise (IOCs) from malware samples including file hashes, network indicators (IPs, domains, URLs), host artifacts (file paths, registry keys, mutexes), and behavioral patterns for threat intelligence sharing and detection rule creation. Activates for requests involving IOC extraction, threat…