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 kensaurus/cursor-kenji --skill docs-coauthorgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/docs-coauthor)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/docs-coauthor"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/docs-coauthor/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/kensaurus/cursor-kenji/docs-coauthor"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/docs-coauthor.svg" alt="Reviewed on agentmods" width="80" 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.03390 |
| Opus 5 | $0.00033 | $0.01695 |
| Sonnet 5 | $0.00013 | $0.00678 |
| Haiku 4.5 | $0.00007 | $0.00339 |
Grade A, and why
docs-coauthor 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Co-Authoring Workflow
Degree of freedom: MIXED. What to ask and what to keep [HIGH freedom];
the three-stage order, six-step section loop, and Reader Testing
[LOW freedom — run exactly].
a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.
Guiding principle — orient the reader before the mechanism. Even a spec, PRD, or RFC should open by answering what this is, why it exists, and who it's for — in plain language — before diving into detail. That's the same reader-first instinct this workflow's Reader Testing stage enforces at the end; apply it from the first sentence. See
docs-writerfor the full "write for the reader's mental model first" rule.
How to reason
- Observe — doc type, audience, desired impact, template or existing draft
- Interpret — what the next reader will lack that the authors already know
- Classify — offer the workflow / work freeform / start at the highest-unknown section
- Test — predict reader questions; a fresh instance must answer them from the doc alone
Worked example
Observe: "write a PRD for billing v2"; no audience named; a Slack thread already rejected a usage-only model. Interpret: that rejection is oral — a pasted PRD will fail when a reader (or a fresh agent) lacks it. Classify: offer the three stages; Context Gathering first (eng + finance; impact = stop re-arguing usage-only). Do not draft the PRD in the first reply.
Self-critique before reporting
- Reader-first open — what / why / who before mechanism
- Fresh-instance test ran — an author reread is not Reader Testing
- User owns the doc — they confirm impact; you do not ship unreviewed
- Right owner — INDEX.md / rejected alternatives →
docs-adr; README prose →docs-writer
When to Offer This Workflow [HIGH freedom]
Trigger conditions:
- User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up"
- User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"
- User seems to be starting a substantial writing task
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 · 374 lines · 66 tokens per session scan A 3c6594c7e57d
docs-coauthor is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 10d ago), licensed MIT. It adds 66 tokens to every session and 3,390 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-09-03.
Other skills, from other repositories
comprehensive-enrichment
Enrich any person or company from any identifier — email, name, LinkedIn URL, domain, company name, Twitter/X handle. Use when asked to enrich, look up, or research a lead, contact, person, or company.
paid-channel-prioritizer
For founders who don't know where to start with paid ads. Analyzes ICP, competitor ad presence, budget constraints, and product type to recommend which 1-2 paid channels to start with and provides a 90-day ramp plan. Prevents the common mistake of spreading a small budget across too many platforms.
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
email-finder-hunter
Email finder and verifier - find emails, verify deliverability, discover companies.
lead-discovery
Orchestrator that runs first for lead generation requests. Gathers business context via website analysis or questions, identifies competitors, builds ICP, and routes to signal skills with pre-filled inputs.
render-mosaic-grid-reveal
Render a 'mosaic-grid-reveal' video from a config — a real-DOM FULL-BLEED N×N mosaic of real product tiles that pops in one tile at a time (scatter order, ease-out-back overshoot), the grid clears, then the brand wordmark builds line-by-line followed by a sub-label, tagline, and CTA; frame-stepped via Playwright and…