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 TashanGKD/tashan-writing-system --skill general-article-writergit clone --depth 1 https://github.com/TashanGKD/tashan-writing-systemWrote 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/tashangkd/tashan-writing-system/general-article-writer)<a href="https://agentmods.dev/skills/tashangkd/tashan-writing-system/general-article-writer"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-writing-system/general-article-writer/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/tashangkd/tashan-writing-system/general-article-writer"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-writing-system/general-article-writer.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.00123 | $0.02681 |
| Opus 5 | $0.00062 | $0.01340 |
| Sonnet 5 | $0.00025 | $0.00536 |
| Haiku 4.5 | $0.00012 | $0.00268 |
Grade A, and why
general-article-writer 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 11d 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.
This is a copy
100% identical to general-article-writer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
通用文章写作 Skill（general-article-writer）
关联知识库：
_内部总控/认知结构/L1_系统性文档/待建维度/写作习惯与风格手册.md（以下简称 WG） 与wechat-article-writer的区别：本 Skill 不做微信 HTML 排版，产出纯 Markdown 草稿
知识导航表（执行前必须理解的概念根）
| 层级 | 文档 | 需要理解的概念 |
|---|---|---|
| D0 认知根（必读） | _内部总控/认知结构/L1_系统性文档/待建维度/写作习惯与风格手册.md（暂用 _内部总控/AI思维碎片/写作习惯与风格手册.md） |
郑总的写作风格：文章结构偏好/语言风格/禁用表达/标题原则/结语要求 |
| D3 规范参考 | .cursor/skills/article-proofreading/SKILL.md（参考审稿标准，非触发执行） |
五轮审稿标准（写稿时对照，不等到最后才审） |
| D4 运行时数据 | — | 若用户提供了初稿，直接作为输入；无初稿则从研究/大纲开始 |
核心概念速查： ① 先大纲确认再写正文：大纲确认后才能开始写，避免方向偏差导致大量返工 ② 挑战者自检 = 写完后以陌生读者视角批判性阅读（「这段话写了什么？论据充分吗？」） ③ 通用长文 = Markdown产出，不做HTML排版（区别于wechat-article-writer）
触发判断（先执行，不可跳过）
IF 用户输入包含「写一篇/帮我写」+ 文章类型关键词（技术/产品/分析/分享/随笔/长文/通用文章）
AND 不含「公众号/推文/他山文章/微信/WeChat」
→ 触发本 Skill
IF 用户说「继续写/补完/下一章」且当前上下文有本 Skill 已生成的草稿
→ 触发本 Skill（进入补全模式，Step 1 识别现有内容，Step 3 直接补全）
IF 不确定是否发公众号（用户提到「分享/对外分享」但未说渠道）
→ 先问「这篇文章是要发到公众号吗？」
- 是 → 切换 wechat-article-writer，不继续本 Skill
- 否 → 继续本 Skill
IF 含「SI/补充材料/LaTeX/推导」→ academic-si-writer 优先，不触发本 Skill
⚡ thin wrapper 转发（优先执行）
本 Skill 已升级为 document-pipeline 的入口。触发后立即转发，不独立执行。
触发后立即执行：
设置 target_format = md
设置 mode = article
转发到 document-pipeline（加载其 SKILL.md，从 Stage 0 开始执行）
Step 0：读取 WG（写作习惯与风格手册）— 写稿前必做，不可跳过
Read: _内部总控/认知结构/L1_系统性文档/待建维度/写作习惯与风格手册.md
提取以下4类约束（按章节标题找，不是猜测）：
① 核心写作哲学——换位思考（从读者决策链倒推结构）/ 结论先行 / 信息密度
② 语言风格禁忌——AI腔清单 / 防守修饰语 / 套话 / 绝对表达
③ 标题写法规范——结论型/问题型（合法）vs 话题描述型（违规），4种错误类型
④ 段落/结构原则——每段有实质内容，信息密度要求
文件不存在或读取失败时：
→ 告知用户「WG 文件未找到，使用默认约束写作（质量可能下降）」
→ 使用以下默认约束继续执行：
- 结论前置（每章节结论放在开头）
- 禁止 AI 腔（不写「核心推论只有一句话」「以下是 N 个要点」等元评论）
- 禁止绝对表达（避免「一定/必须/完全/最」等）
- 读者视角（先问读者是谁、关心什么，再决定结构）
Step 1：确认文章类型、读者与长度
若用户在触发消息中已明确提供这3项信息 → 直接确认并进入 Step 2，不重复询问。 否则，一次性询问（不分多轮）：
文章类型（影响结构）：
| 类型 | 典型场景 |
|---|---|
| A. 技术分析 | 框架对比/系统设计/方案评估/工具调研 |
| B. 产品思考 | 产品设计/商业分析/战略判断/洞察记录 |
| C. 对外分享 | 演讲稿/培训文档/向不了解背景的读者解释某事 |
| D. 个人随笔 | 思考记录/反思/实验性写作（结构自由） |
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.
- 11d ago First seen · 206 lines · 123 tokens per session scan A 26d7c3d7b5ce
general-article-writer is a skill published in the GitHub repository TashanGKD/tashan-writing-system (2 stars, last pushed 5mo ago), licensed MIT. It adds 123 tokens to every session and 2,681 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to general-article-writer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…