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 Grid0723/skills --skill edit-articlegit clone --depth 1 https://github.com/Grid0723/skillsWrote 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/grid0723/skills/edit-article)<a href="https://agentmods.dev/skills/grid0723/skills/edit-article"><img src="https://agentmods.dev/badge/skills/grid0723/skills/edit-article/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/grid0723/skills/edit-article"><img src="https://agentmods.dev/badge/skills/grid0723/skills/edit-article.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.00044 | $0.00287 |
| Opus 5.5 | $0.00018 | $0.00115 |
| Sonnet 5.5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
edit-article 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.
What it actually says
edit-article
成品文章的编辑润色。DAG 依赖顺序逐段重写。
Leading Words
| 术语 | 定义 |
|---|---|
| DAG 依赖顺序 | 先编辑被其他段引用最少的段——改了 A 不会破坏 B |
| 逐段重写 | 每段独立编辑，确认后进入下一段 |
步骤
1. 按 H2 拆分 → 构建依赖图
段落 A 引用了 B 中的概念 → A 依赖 B。
2. 按依赖从少到多重写
每段：展示原稿 → 指出可改进处 → 用户确认 → 重写。
- 完成标准：全部段落重写完毕
3. 完整性检查
所有段间引用仍有效，风格一致。
外部参考
references/edit-examples.md— DAG 构建示例、重写前后对比、常见编辑错误
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.
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.
- 1mo ago First seen · 36 lines · 44 tokens per session scan A 4fd236ff59aa
edit-article is a skill published in the GitHub repository Grid0723/skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 287 once invoked, about $0.0002 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.
Other skills, from other repositories
backlog-md
Task tracking system for agents via Backlog.md CLI. Use when creating deferred issues during implementation, filing audit findings, working assigned tasks, or managing project work. Optimized for agent workflows: structured issue filing, priority/labeling system, and task completion tracking.
create-stories
Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.