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/verdikta/verdikta-applications/documentation-standardsgit clone --depth 1 https://github.com/verdikta/verdikta-applicationsWrote 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/verdikta/verdikta-applications/documentation-standards)<a href="https://agentmods.dev/rules/verdikta/verdikta-applications/documentation-standards"><img src="https://agentmods.dev/badge/rules/verdikta/verdikta-applications/documentation-standards.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.01595 | $0.01595 |
| Opus 5 | $0.00797 | $0.00797 |
| Sonnet 5 | $0.00319 | $0.00319 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
documentation-standards 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 5d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
Documentation Structure
Essential Documents
- README.md - User-facing overview, quick start, features
- PROJECT-OVERVIEW.md - Architecture, concepts, data models
- CURRENT-STATE.md - Implementation status, setup instructions
- DEVELOPER-GUIDE.md - Quick reference for developers
- DESIGN.md - Complete technical specification
When to Create New Docs
Create new documentation when:
- Adding a major feature (e.g., MULTI-FILE-SUBMISSION-GUIDE.md)
- Implementing complex workflow (e.g., TESTING-GUIDE.md)
- Consolidating information (e.g., IMPLEMENTATION-SUMMARY.md)
Don't create docs for:
- Minor bug fixes
- Small UI tweaks
- Internal refactoring
Update Checklist
When Adding Features
- Update README.md with feature description
- Update CURRENT-STATE.md with implementation status
- Add to DEVELOPER-GUIDE.md if it's a new pattern
- Create feature-specific guide if complex
- Update relevant section in DESIGN.md
When Changing Architecture
- Update PROJECT-OVERVIEW.md
- Update DESIGN.md
- Update any affected diagrams
- Note in CURRENT-STATE.md
When Fixing Bugs
- If significant, note in CURRENT-STATE.md
- Update TROUBLESHOOTING section if applicable
- No need to update for minor fixes
Document Formatting
Headers
# Main Title (H1 - only one per document)
## Section (H2)
### Subsection (H3)
#### Minor Section (H4)
Code Blocks
Always specify language:
```javascript
const example = "code";
```
```bash
npm install
```
```json
{
"key": "value"
}
```
File References
Use absolute paths from repo root:
See [archiveGenerator.js](example-bounty-program/server/utils/archiveGenerator.js)
Status Indicators
Use emoji for quick status:
✅ Complete - Feature is done and tested
🔄 In Progress - Currently working on
⏳ Pending - Planned but not started
❌ Blocked - Cannot proceed
⚠️ Needs Attention - Issues to resolve
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.
- 5d ago First seen · 317 lines · 1,595 tokens per session scan A 6ca64d1d5e90
documentation-standards is a cursor rule published in the GitHub repository verdikta/verdikta-applications (24 stars, last pushed yesterday), licensed MIT. It adds 1,595 tokens to every session, about $0.0080 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-08-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.