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/universal)<a href="https://agentmods.dev/rules/ackeskin/contexture/universal"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/universal/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/universal"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/universal.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.00012 | $0.09637 |
| Opus 5.5 | $0.00005 | $0.03855 |
| Sonnet 5.5 | $0.00002 | $0.01927 |
| Haiku 4.5 | $0.00001 | $0.00964 |
Grade A, and why
universal 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 — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated from
architectural-rules/universal/— do not hand-edit.
Autonomy default
The default autonomy posture for this project is balanced effort / stop-at-criteria-met / ask-only-on-forks (the typed values live in this file's autonomy: frontmatter). It is the lowest tier of the autonomy contract's precedence (live > kickoff > inferred > default > implicit-default): a per-task /autonomize kickoff or a live steer overrides it; absent both, this is what the workflow organs read. See autonomize.
Override this default per project by placing an autonomy-default.md in the user or project overlay tier (~/.claude/architectural-rules/universal/ or <repo>/.claude/rules/universal/) with a different autonomy: block — the standard overlay cascade (project > user > shipped) applies, no parallel config engine. /autonomize's save-as-default flow writes the project-tier file for you.
/autonomize and the organs read the typed autonomy: frontmatter values from the resolved file directly — not via the rule-body resolver (resolve-rules.js), which emits prose bodies for priming and does not carry custom frontmatter keys. This file is a rule (it lives in the overlay tree for cascade + override + disable) whose payload is its frontmatter, not its body. relevance: on-demand keeps it off the always-on floor — the values are read when the contract resolves, never paid every turn.
Canonical tool commands
Pin the command next to the verb, not just the verb. The verb is the
policy ("read PR comments"); the command is the implementation. Re-deriving the
flags every session is a tax that pays nothing — the answer is the same each
time, and a wrong improvisation (missing --paginate, truncated output) is a
silent failure the agent won't notice.
Resolution order: a project's CLAUDE.md ## Canonical commands section (or
<repo>/.claude/canonical-commands.md) wins; these universal pins fill in; if no
pin exists, improvise as usual — no degradation.
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 · 420 lines · 12 tokens per session scan A 8b8638e8fe5c
universal is a cursor rule published in the GitHub repository AcKeskin/contexture (2 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 9,637 once invoked, about $0.0000 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-10-27.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.