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.
git 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/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/rules/danielvm-git/bigpowers/edit-document"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/edit-document.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.00046 | $0.00235 |
| Opus 5.5 | $0.00018 | $0.00094 |
| Sonnet 5.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 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 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.
- 1mo ago 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 (267 stars, last pushed 27d ago), licensed MIT. It adds 46 tokens to every session and 235 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
general
API design standards — treat the API as a consumer-facing contract. Apply when designing, reviewing, or changing HTTP endpoints, routes, controllers, request/response payloads, and API resources.
00-project-rules
ContextOS core project rules and role orchestration.
vue
Rules for Vue (2 and 3) single-file components.
context-os
ContextOS rules for context-os.