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 agentmods add rules/danielvm-git/bigpowers/edit-documentgit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/edit-document)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/edit-document"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/edit-document.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00235 |
| Opus 5 | $0.00023 | $0.00118 |
| Sonnet 5 | $0.00009 | $0.00047 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
edit-document 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 today.
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 Document
Distinct from write-document: Use this skill when the document already exists and needs restructuring, clarity, or prose improvements. Use write-document to create a document from scratch.
HARD GATE — Document edits must preserve intent and accuracy. Do NOT remove or contradict existing content without understanding why it was written. Check git history for context.
Process
- First, divide the document into sections based on its headings. Think about the main points made in each section.
Consider that information is a directed acyclic graph, and that pieces of information can depend on other pieces of information. Make sure that the order of the sections and their contents respects these dependencies.
Confirm the sections with the user.
- For each section:
2a. Rewrite the section to improve clarity, coherence, and flow. Use maximum 240 characters per paragraph.
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.
- today First seen · 23 lines · 46 tokens per session scan A 883ea14afa0f
edit-document is a cursor rule published in the GitHub repository danielvm-git/bigpowers (162 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 235 once invoked, about $0.0002 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 cursor rules, from other repositories
document-lifecycle-guard
文档生命周期守门规则。适用于所有产品开发角色（产品经理/技术架构师/测试工程师/DevOps）激活时。规定了每个角色如何管理自己的项目文档：自建文件夹、in-place更新、追加变更记录、重大改版存旧版。禁止创建「产品定义v2.md」「新版技术架构.md」等并行版本文件。.
document-path-resolver
Cursor rule "document-path-resolver" from TashanGKD/tashan-cursor-skills, covering 文档路径解析规则（document-path-resolver）, 触发条件, 执行步骤, 默认路径表（无 project-config.md 时使用） and project-config.md 格式规范.
document-reference-guard
文档引用留痕与级联更新规则（F-033/F-034）。当任何文档被引用（在 Skill/Rule/其他文档中用路径引用）、或已引用的文档被移动/更新/版本化/归档时自动激活。强制执行：① 引用留痕（被引用文档追踪其引用方）② 级联更新（文档变动必须传播到所有引用方）。.
document
Cursor rule "document" from flyeric0212/cursor-rules, covering 文档规范, readme.md 规范, changelog.md 规范, v1.0.0 and 文档更新原则.
van-file-verification
Visual process map for VAN mode file verification.
citazioni
Citazioni corrette (stile numerico) e bibliografia coerente per tesi triennale in LaTeX.