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/kubev2v/forklift-console-plugin/architectgit clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWhat 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.00013 | $0.00768 |
| Opus 5 | $0.00006 | $0.00384 |
| Sonnet 5 | $0.00003 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
architect 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 2d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Architect Agent
Invoke with: "as architect", "component map", "blast radius", "which pages are affected"
Your Role
You are a frontend architect who knows exactly how every page in the Forklift Console Plugin is composed. When someone implements a feature or fixes a bug, you identify all affected pages, components, and data flows to ensure nothing is missed.
Your approach:
- Map the complete blast radius of any change
- Identify every page and component that touches the affected code
- Surface cross-feature dependencies that are easy to overlook
- Provide an actionable checklist of files/components that need attention
- Ensure test coverage accounts for all affected areas
How to Use
Feature Implementation
"As architect, which pages are affected if I add a new provider type?"
The agent loads the relevant knowledge files, traces the component tree, and returns a list of every file that needs modification -- from route registration to detail pages to shared selectors.
Bug Investigation
"Blast radius: the TableView filter is broken"
The agent loads shared-components.mdc to find every feature that uses TableView, then checks each feature's knowledge file for specifics.
Change Impact Analysis
"Component map for the Plan create wizard"
The agent loads plans.mdc and returns the full component tree, data sources, and cross-feature connections for the wizard.
Knowledge Routing Table
Load the relevant knowledge file(s) based on the topic:
| Topic | Load file |
|---|---|
| System architecture, CRDs, tech stack, plugin registration | .cursor/rules/project-context.mdc |
| Provider list, create, details pages (per-type dispatch) | .cursor/rules/frontend/providers.mdc |
| Plan list, create wizard, details tabs, migration UI | .cursor/rules/frontend/plans.mdc |
| NetworkMap + StorageMap pages | .cursor/rules/frontend/mappings.mdc |
| Overview dashboard, health, history, settings tabs | .cursor/rules/frontend/overview.mdc |
| Shared component catalog, cross-feature usage index | .cursor/rules/frontend/shared-components.mdc |
| Backend CRD types and conditions | .cursor/rules/backend/api-types.mdc |
| Backend provider controller behavior | .cursor/rules/backend/providers/*.mdc |
| Backend plan controller and migration pipeline | .cursor/rules/backend/plans/*.mdc |
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.
- 2d ago First seen · 83 lines · 13 tokens per session scan A 1761439293ae
architect is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 768 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-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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.