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/AcKeskin/contextureWrote 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/ackeskin/contexture/web)<a href="https://agentmods.dev/rules/ackeskin/contexture/web"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/web/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/ackeskin/contexture/web"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/web.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.00000 | $0.00498 |
| Opus 5.5 | $0.00000 | $0.00199 |
| Sonnet 5.5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
web 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 today.
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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated from
architectural-rules/web/— do not hand-edit.
Web async discipline
- All async work is explicit.
async/awaitat call sites, not fire-and-forget. - No implicit side effects in render / effect hooks beyond what the contract allows (e.g. React
useEffectcleanup). - Cancelation is part of the design — every long-running async operation has a cancel path (AbortController, effect cleanup, subscription disposal).
- Errors in async work are handled explicitly. Unhandled promise rejections are bugs, not warnings to ignore.
Why: async bugs dominate production incidents in web apps. Explicit patterns catch them at review time. Source: MDN AbortController; WHATWG HTML unhandledrejection.
Web layering
- Four layers, strict dependencies inward:
- Domain — pure business logic, framework-agnostic.
- State — application state shape, reducers / stores.
- Transport — HTTP, WebSocket, other I/O adapters.
- UI — presentation, framework components.
- Domain must have no React / Vue / Angular / framework imports.
- UI talks to State; State talks to Transport; Transport talks to Domain types (not the other way).
- Avoid magic globals. No module-level mutable state.
- This vocabulary refines universal/layering for web apps: Domain = Core, Transport = Integration, UI = UI; State is web's extra layer between UI and Transport (Platform rarely appears). Universal/layering owns the base vocabulary.
Why: frameworks churn. Domain logic bound to framework primitives dies with the framework. Source: ports-and-adapters / clean-architecture layering.
Web state flow
- State flow is predictable: state in → render out → action → state in. Unidirectional.
- No magic globals. No
window.*mutation for app state. - State changes are explicit and traceable — every change has an identifiable source (action, event handler, effect).
- Prefer derived state over duplicated state. If two pieces of state can disagree, one is wrong.
Why: state bugs are the hardest to reproduce. Predictable flow is the minimum insurance. Source: Flux / Redux unidirectional-data-flow docs.
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.
- today First seen · 40 lines · 498 tokens per session scan A 3bebbbea97d2
web is a cursor rule published in the GitHub repository AcKeskin/contexture (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 498 tokens. 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-10-27.
Other cursor rules, from other repositories
hatch3r-observability-logging
Structured logging and error reporting conventions for the project.
debug
Command: /debug - Run the debug workflow for this project.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.