Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/event4u-app/agent-confignpx agentmods add skills/event4u-app/agent-config/doc-coauthoringWrote 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/event4u-app/agent-config/doc-coauthoring)<a href="https://agentmods.dev/skills/event4u-app/agent-config/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/doc-coauthoring/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/event4u-app/agent-config/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/doc-coauthoring.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.00053 | $0.02056 |
| Opus 5 | $0.00026 | $0.01028 |
| Sonnet 5 | $0.00011 | $0.00411 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
doc-coauthoring 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 8d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-coauthoring
When to use
Cross-surface handoff. When this document consumes upstream work (research → document, spreadsheet → report), read the handoff envelope from
surface-agent-contracts: trustverification_already_done, honour source restrictions, and don't re-fetch what the source already grounded.
Use this skill when:
- User starts a substantial writing task — PRD, RFC, design doc, decision doc, technical spec, proposal
- User says "help me write this up", "draft a proposal", "we need a doc for X"
- The output is a structured prose document the user will own and ship
Do NOT use when:
- Authoring agent docs / module docs / AGENTS.md →
agent-docs-writing - Writing a README →
readme-writing/readme-writing-package - Writing an ADR (process is fixed, no co-authoring loop) →
adr-create - Code documentation, inline comments, docstrings
Goal
Move from a fuzzy ask to a complete document the user owns, by:
- Closing the context gap before drafting
- Building each section through brainstorm → curate → draft → refine
- Testing the draft with a fresh-context reader before declaring done
Preconditions
- User explicitly wants a document (not a quick answer)
save-fileandstr-replace-editoravailable- Target path and filename agreed up front
Document format & export floor
The document surface's floor (per
surface-agent-contracts):
- Choose the format by intent. Markdown vs
.docxvs PDF follows what the user will DO with it — when a named format is requested, produce THAT format via the document tooling; never silently substitute markdown for a.docxrequest. (fixture:ssac-docx-requested-markdown-only.) - Preserve edit scope. On an edit, change only what was asked and preserve
the rest of the document (mirrors
minimal-safe-diff). - Print/PDF preserves selectable text. Never rasterize a text-heavy document
to an image-only PDF when browser print or native export keeps the text
selectable. (fixture:
ssac-pdf-screenshot-rasterized.) - Verify the output opens/exports. Confirm the generated file opens /
round-trips
(
design-artifact-verification); where the format's tooling is absent, ship the source + say what could not be verified rather than claiming a produced file.
What ships with it
2 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.
- 8d ago First seen · 163 lines · 53 tokens per session scan A 3be3e0a6b7e2
doc-coauthoring is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 2,056 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
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.