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 cnfeat/top-pm-skills --skill docx-tracked-changesgit clone --depth 1 https://github.com/cnfeat/top-pm-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/cnfeat/top-pm-skills/docx-tracked-changes)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/docx-tracked-changes"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/docx-tracked-changes/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/cnfeat/top-pm-skills/docx-tracked-changes"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/docx-tracked-changes.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.00093 | $0.01220 |
| Opus 5 | $0.00046 | $0.00610 |
| Sonnet 5 | $0.00019 | $0.00244 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
docx-tracked-changes 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 6d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Word Doc Tracked Changes Skill
Produces properly-structured tracked changes for a Word document — insertions, deletions, replacements, and margin comments formatted so they can be applied directly to the source document. Built to leverage Opus 4.7 improvements in .docx redlining and tracked changes generation.
Required Inputs
Ask the user for these if not provided:
- The document (paste the text or upload the .docx)
- Review type (legal review / copy edit / substantive rewrite / compliance check / plain English rewrite)
- Review scope (full document / specific sections / specific clause type)
- Reviewer role (author / manager / legal counsel / subject matter expert)
Output Structure
1. Redline Summary
Document: [Name or identifier] Review type: [As stated] Reviewer: [Role] Total changes: [Insertions: N / Deletions: N / Comments: N] Overall assessment: [1-2 sentences — is this document close to final, or does it need substantial revision?]
2. Top-Level Changes
Changes that affect the meaning or structure of the document:
Change N — [Section or paragraph reference]
- Original: "[Exact original text]"
- Suggested: "[Proposed new text]"
- Reason: [Why this change — substantive/legal/clarity]
3. Line-by-Line Tracked Changes
For each paragraph that needs changes, format as:
[Paragraph reference — e.g. "Section 3, Paragraph 2"]
Original:
[Exact original paragraph]
Tracked changes:
[Same paragraph with deletions marked as
strikethroughand insertions marked as bold]
Clean version:
[Final clean text after applying changes]
4. Margin Comments
Comments that flag issues without proposing a specific wording change:
Comment N — [Location] "[Comment text — written as the reviewer would write it. Direct, specific, actionable.]"
Comments are for things like:
- "This clause conflicts with Section 7 — please reconcile"
- "Missing definition of [term] used throughout"
- "Confirm figure with finance team"
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.
- 6d ago First seen · 129 lines · 93 tokens per session scan A 0855623715e9
docx-tracked-changes is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 1,220 once invoked, about $0.0005 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
patent-reader
A plain-language reader for Chinese patents that turns a publication number or PDF into notes, diagrams, and an Obsidian entry. Obsidian is a note-taking app that stores linked Markdown files.
meta-pdf-reformat-pipeline
Modernize a legacy PDF: structural extraction → natural-language rewrite of problem pages → audit summary → re-merge into the final PDF.
software-copyright-materials
A workflow for creating Chinese application materials for software copyright registration from a real software project.
ectd-xml-compiler
Automatically convert uploaded drug application documents (Word/PDF) into XML skeleton structure compliant with eCTD 4.0/3.2.2 specifications.
audit-export
Export the full CocoAudit trail as a stakeholder-ready compliance document.
software-certificate-skill
An automated workflow for preparing Chinese software-copyright registration materials from a real software project. It produces application information, an operation manual, and source-code documents with evidence from the project.