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/robotaitai/project-bedrock/generate-architecture-docgit clone --depth 1 https://github.com/robotaitai/project-bedrockWrote 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/robotaitai/project-bedrock/generate-architecture-doc)<a href="https://agentmods.dev/rules/robotaitai/project-bedrock/generate-architecture-doc"><img src="https://agentmods.dev/badge/rules/robotaitai/project-bedrock/generate-architecture-doc.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.1 | $0.00033 | $0.01040 |
| Opus 5 | $0.00016 | $0.00520 |
| Sonnet 5 | $0.00007 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
generate-architecture-doc 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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Architecture HTML Document
When asked to create an architecture document for a Cramim package, produce a self-contained HTML file in architecture_docs/ following this process.
1. Research the Package
Before writing anything, thoroughly investigate the target package:
- Read all
.hppand.cppfiles in the package - Read
package.xmlandCMakeLists.txtfor dependencies - Read any config/YAML files referenced by launch files
- Grep for
create_publisher,create_subscription,create_service,create_clientto find all ROS interfaces - Grep for state definitions (
State::createStateSharedPtr, enums, or equivalent patterns) - Trace the full data flow from inputs to outputs
- Identify all inter-node communication patterns
- Read launch files to understand how the node is started and configured
2. Required Content Sections
Every architecture doc must include:
- Executive summary — what the component does, 2-3 sentences, with role badges for related components
- Table of contents with anchor links
- Architecture diagram — where this component fits in the overall Cramim system (Mermaid flowchart)
- State machine (if applicable) — Mermaid
stateDiagram-v2with all states and transitions - State details —
on_enter,in_state,on_exitcallbacks for each state (table per state) - Transition table — every transition with From, To, Condition, Side Effect columns
- End-to-end flow — Mermaid
sequenceDiagramshowing the main operational flow - Topics & services — tables for published topics, subscribed topics, provided services, called services (columns: name, type, description)
- Interactions with other nodes — summary cards showing who talks to whom
- Key design decisions — bullet list of architectural choices and why
- File structure — annotated directory tree in a
<pre>block
3. Visual Style
Use the exact dark-theme style from the reference file architecture_docs/dc_behavior_tree_workplan.html:
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.
- 6d ago First seen · 88 lines · 33 tokens per session scan A 03c373568b8f
generate-architecture-doc is a cursor rule published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 16d ago), licensed MIT. It adds 33 tokens to every session and 1,040 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-08-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.