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/write-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/write-document)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/write-document"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/write-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.00048 | $0.02307 |
| Opus 5 | $0.00024 | $0.01154 |
| Sonnet 5 | $0.00010 | $0.00461 |
| Haiku 4.5 | $0.00005 | $0.00231 |
Grade A, and why
write-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.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Document (BMAD)
Create high-signal technical documentation that serves as an expert collaborator for both humans and AI. This skill enforces the BMAD principles to prevent context rot and ensure architectural durability.
Distinct from edit-document: Use this skill to create a document that does not yet exist. Use edit-document when a document already exists and needs restructuring, clarity, or prose improvements.
HARD GATE — Every document must have a clear "Reason for Existence." If a document doesn't provide actionable leverage for a caller or test, do not create it.
The BMAD Principles
| Principle | Execution |
|---|---|
| Bold | Make strong assertions. Define clear boundaries and "Never" rules. No "it might" or "usually." |
| Minimal | High-density, low-filler. Circuit Breaker: If the file exceeds 300 lines or the session exceeds 20 turns, you MUST run terse-mode and compact state before saving. |
| Actionable | Link every doc to a verifiable outcome. Architectural Docs: Verify via Gherkin features (specs/verifications/features/) or grep-based structure checks (grep -c "pattern" file) that prove the design's constraints are present. |
| Durable | Design for the long-term. Scalability: Use "Nested Indexing"—root files link to module-level GEMINI.md indexes; do not list individual sub-files in the root. |
Process
1. Identify the Artifact Type & Scope
Choose the correct BMAD-BigPowers artifact:
- Decision Record (ADR): For "Why" decisions (saved to
specs/adr/). - Context Map: For system-wide architectural mapping (
specs/tech-architecture/tech-stack.md). - Technical Guide: For "How-to" with verification (saved to
<module>/REFERENCE.md). - Behavioral Feature: Gherkin-style compliance specs (saved to
specs/verifications/features/). - Project README: Project-facing documentation (saved to
README.mdat project root).
Cross-Cutting Concerns: If a doc affects multiple modules, place the authoritative source in the lowest common ancestor directory and use "Delegates" (one-line pointers) in sub-directories to maintain the Single Source of Truth without violating the Stepdown Rule.
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 · 281 lines · 48 tokens per session scan A 5504bfa7134e
write-document is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 2,307 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.
swift
Swift patterns: SwiftUI, actors, async/await, value types.