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.
git clone --depth 1 https://github.com/lucamezzalira/mfe-skillsWrote 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/lucamezzalira/mfe-skills/mfe-architecture-canvas-pointer)<a href="https://agentmods.dev/rules/lucamezzalira/mfe-skills/mfe-architecture-canvas-pointer"><img src="https://agentmods.dev/badge/rules/lucamezzalira/mfe-skills/mfe-architecture-canvas-pointer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/lucamezzalira/mfe-skills/mfe-architecture-canvas-pointer"><img src="https://agentmods.dev/badge/rules/lucamezzalira/mfe-skills/mfe-architecture-canvas-pointer.svg" alt="Reviewed on agentmods" width="80" 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.00361 | $0.00361 |
| Opus 5.5 | $0.00144 | $0.00144 |
| Sonnet 5.5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
mfe-architecture-canvas-pointer 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 2mo 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.
What it actually says
Micro-Frontend Canvas — external skill
Version: 1.0 | Skill: understanding-mfe-architecture
This repository covers boundary governance (eight rules, review, routing, composition decisions). The Micro-Frontend Canvas — worksheet structure, facilitation steps, and iteration templates — is maintained in a separate skill.
When to use the Canvas skill (not this repo)
- The team has identified a domain but has not documented implementation decisions per MFE
- Cold start is blocked: ownership or boundary is unclear before code
- You need a facilitated session: one micro-frontend, one canvas iteration
When to stay in mfe-skills
- Adoption and organisational readiness
- Boundary validity and the eight rules
- Shell/MFE integration review and remediation
- URL routing ownership and platform vs domain events
Install the Canvas skill
Use the dedicated micro-frontend-canvas skill (separate repository):
- Repository: https://github.com/lucamezzalira/mfe-canvas
- Learn more: https://www.buildingmicrofrontends.com
Do not load full Canvas facilitation content from this repo. If the Canvas skill is not installed, tell the user to install it before running a Canvas session.
Canvas threshold (defined here)
Governance in this repo still uses the Canvas threshold: fewer than 5 props exposed to the container, identifiers not domain objects. Validate that in boundary-design.md and reviewing-mfe-boundaries. The worksheet itself belongs in the Canvas skill.
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.
- 2mo ago First seen · 38 lines · 361 tokens per session scan A b34ccfd6d0b8
mfe-architecture-canvas-pointer is a cursor rule published in the GitHub repository lucamezzalira/mfe-skills (53 stars, last pushed 1mo ago), licensed MIT. It adds 361 tokens to every session, about $0.0014 per session on Opus 5.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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.