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/aetox-skills/docstruct/docstructgit clone --depth 1 https://github.com/aetox-skills/docstructWhat 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.00020 | $0.00138 |
| Opus 5 | $0.00010 | $0.00069 |
| Sonnet 5 | $0.00004 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
docstruct 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 yesterday.
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
DocStruct Cursor Rule
When creating, updating, or auditing documentation:
- Read existing docs before writing.
- Update existing files before creating new files.
- Create a new doc only when it has a clear responsibility.
- Keep one source of truth for each durable fact.
- Link instead of copying details.
- Mark uncertain information as
UNKNOWN. - Mark required work as
TODO. - Keep docs short unless complexity requires detail.
- Do not invent missing implementation details.
- Avoid empty placeholder files.
Use the smallest structure that preserves clarity, ownership, and continuity.
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.
- yesterday First seen · 21 lines · 20 tokens per session scan A 9a6a56c9ecb0
docstruct is a cursor rule published in the GitHub repository aetox-skills/docstruct (1 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 138 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
cursorrules
TypeScript + esbuild + VS Code Webview API.
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
write
Writing style guide with AI detection avoidance. For tweets, LinkedIn, blogs, READMEs, commits. Activate with @write.
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.
typescript
TypeScript and Node.js conventions for Textrawl.
unity-performance
Cursor rule "unity-performance" from Common-ka/ai-agent-unity-rules, covering unity performance rules, update/fixedupdate/lateupdate, usage rules, object pooling (unityengine.pool) and addressables (not resources).