writing-cc

writing-cc is a skill for Claude Code, Codex from zjYao36/markdown-claude-code. It costs 110 tokens per session (4,410 once invoked), scanned A, original, MIT.

A document-writing workflow that researches a topic, drafts a document, and iteratively reviews it against criteria derived from the request. It is designed for producing a polished guide, summary, or other substantial document.

In plain words
What is it for?
Use it when you need a researched guide, summary, or other high-quality document and want review rounds before the final draft.
Why use it?
It turns a broad writing request into explicit quality checks and revisions. Claims and examples are grounded in web sources, local material, or cited papers.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it when you need a researched guide, summary, or other high-quality document and want review rounds before the final draft.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zjyao36/markdown-claude-code/writing-cc
Install

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.

Any agent
npx skills add zjYao36/markdown-claude-code --skill writing-cc
Clone the repo
git clone --depth 1 https://github.com/zjYao36/markdown-claude-code

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for writing-cc

README.md
[![agentmods](https://agentmods.dev/badge/skills/zjyao36/markdown-claude-code/writing-cc/github.svg)](https://agentmods.dev/skills/zjyao36/markdown-claude-code/writing-cc)
Your own site
<a href="https://agentmods.dev/skills/zjyao36/markdown-claude-code/writing-cc"><img src="https://agentmods.dev/badge/skills/zjyao36/markdown-claude-code/writing-cc/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.

agentmods 80×15 button for writing-cc

Your own site · 80×15
<a href="https://agentmods.dev/skills/zjyao36/markdown-claude-code/writing-cc"><img src="https://agentmods.dev/badge/skills/zjyao36/markdown-claude-code/writing-cc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,410 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00110 $0.04410
Opus 5.5 $0.00044 $0.01764
Sonnet 5.5 $0.00022 $0.00882
Haiku 4.5 $0.00011 $0.00441

Measured 1mo ago against content hash 830546e5ca94, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

writing-cc 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 1mo 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.

writing-cc/SKILL.md · 517 lines

How it starts

The opening of the file, as written. The whole thing — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing-CC: Automated Document Writing with Iterative Review

Write and refine: $ARGUMENTS

Overview

Use this skill when the user wants a polished, well-researched written document on any topic. The skill does not simply write and hand off. It first understands what makes the document valuable, derives measurable evaluation criteria, writes a grounded first draft, then runs it through an external GPT reviewer using those exact criteria — iterating until the document meets the bar or MAX_ROUNDS is reached.

Three principles dominate:

  1. Requirements first, writing second. Extract what the user actually needs before producing a single word of content.
  2. Criteria-driven quality. Every evaluation round uses the same rubric derived from the user's requirements — not generic writing advice.
  3. Grounded writing. All claims and examples must come from real sources: web search, local materials, or cited papers. Never fabricate examples.
User input (document request)
  -> Phase 0 (Claude): Analyze requirements — purpose, audience, key points, constraints
  -> Phase 1 (Claude): Derive evaluation rubric (5-7 measurable criteria) from requirements
  -> Phase 2 (Claude): Research (web search + local materials) + write first draft
  -> Phase 3 (Codex/GPT): Score draft on rubric, provide structured feedback
  -> Phase 4 (Claude): Parse feedback, revise document
  -> Phase 5 (Codex, same thread): Re-score revised document
  -> Repeat Phase 4-5 until OVERALL SCORE >= SCORE_THRESHOLD or MAX_ROUNDS reached
  -> Phase 6: Save full history to writing-logs/

Constants

  • REVIEWER_MODEL = gpt-5.4 — Reviewer model used via Codex MCP.
  • MAX_ROUNDS = 5 — Maximum review-revise cycles.
  • SCORE_THRESHOLD = 8.5 — Minimum overall score to stop early.
  • OUTPUT_DIR = writing-logs/ — Directory for all output files.
  • MAX_SEARCH_QUERIES = 10 — Maximum web search queries during research.
  • MAX_LOCAL_FILES = 10 — Maximum local files to scan for grounding.

Read the full file on GitHub · 517 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 1mo ago First seen · 517 lines · 110 tokens per session scan A 830546e5ca94

Subscribe to this mod's changes

writing-cc is a skill published in the GitHub repository zjYao36/markdown-claude-code (5 stars, last pushed 7mo ago), licensed MIT. It adds 110 tokens to every session and 4,410 once invoked, about $0.0004 per session on Opus 5.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-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens