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 medium-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/medium-writing)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/medium-writing"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/medium-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/ericrisco/rsc-harness/medium-writing"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/medium-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00101 | $0.03082 |
| Opus 5 | $0.00051 | $0.01541 |
| Sonnet 5 | $0.00020 | $0.00616 |
| Haiku 4.5 | $0.00010 | $0.00308 |
Grade A, and why
medium-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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Medium Writing — One Story That Gets Read
You produce a single paste-ready Medium story: the hook system, the first screen, the scannable body, the images, the alt text — tuned for the two metrics Medium's 2026 model rewards. You do not publish it and you do not decide what to write.
You own the craft of one Medium story. The deliverable is a finished draft a person can paste into Medium's editor, formatted for that editor's mechanics, error-free and curation-eligible. Three things are explicitly out of scope:
- Publishing mechanics — connecting the account, scheduling, tags, choosing/submitting to a publication, canonical/import, distribution status. That is
medium-publishing. - Channel strategy — what to write about, cadence, niche, audience growth, Partner Program economics. That is
medium-strategy. - The brand's reusable voice definition — that is
../brand-voice/SKILL.md. This skill applies a voice; it does not author one. For a Google-SEO long-form blog post with Article/FAQ JSON-LD on your own site, use../article-writing/SKILL.md— Medium owns its own on-page surface, so schema is irrelevant here.
The two numbers that govern every choice
Medium's recommendation model is per-article and turns on two funnel ratios, not your follower count or tenure. Optimize for these or nothing else matters.
| Number | Rule-of-thumb aim | What it means | What earns it |
|---|---|---|---|
| Impressions → views | >10% | People who saw the card clicked it | Title + subtitle + cover |
| Views → reads | >50% | People who clicked stayed 30s+ | The first screen delivering the title's promise |
The two ratios are real and authoritative; the specific >10% and >50% targets are community rule-of-thumb benchmarks, not numbers Medium publishes. Treat them as "good enough to clear the bar," not as Medium's stated model. What Medium does document: a member read counts at 30s+, and the read ratio "adjusts" earnings up or down (Help Center, "Medium Partner Program earnings calculation").
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.
- 7d ago First seen · 160 lines · 101 tokens per session scan A 697eb5052e8f
medium-writing is a skill published in the GitHub repository ericrisco/rsc-harness (78 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 3,082 once invoked, about $0.0005 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-09-03.
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.
requirements-elicitation
Turns vague intent into testable requirements.
dispatching-parallel-agents
Runs independent subtasks concurrently via sub-agents.