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/cpp)<a href="https://agentmods.dev/rules/ackeskin/contexture/cpp"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/cpp/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/cpp"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/cpp.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.03811 |
| Opus 5.5 | $0.00000 | $0.01524 |
| Sonnet 5.5 | $0.00000 | $0.00762 |
| Haiku 4.5 | $0.00000 | $0.00381 |
Grade A, and why
cpp 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated from
architectural-rules/cpp/— do not hand-edit.
C++ concurrency
Use RAII lock guards (std::lock_guard, std::scoped_lock, std::unique_lock) — never bare mutex.lock() / unlock(). A manual unlock is skipped on every early return and every throw. (CP.20)
Acquire multiple locks with std::scoped_lock (or std::lock) in one statement — it orders acquisition to avoid deadlock. Never hand-order two lock_guards. (CP.21)
Never call unknown / user-supplied code while holding a lock — it may re-enter and deadlock, or block far longer than intended. (CP.22)
Use std::atomic for cross-thread flags and counters. volatile is not a synchronization primitive — it has no memory-ordering guarantees. (CP.8)
Do not write lock-free code unless you must and have measured the need. Assume your lock-free code is wrong until proven otherwise with tooling. (CP.100)
Minimize sharing of writable data. The cheapest concurrency bug is the one that can't happen because nothing is shared. (CP.3)
Why: concurrency bugs are non-deterministic and survive code review and most tests — RAII locking and atomics remove whole classes of them by construction. Source: C++ Core Guidelines (CP).
C++ const-correctness
Declare objects const unless the value must change. Immutable-by-default makes the few mutable things visible and lets the compiler enforce the rest. (Con.1)
Make member functions const when they don't modify observable state. A non-const method is a claim that it mutates — don't make that claim falsely. (Con.2)
Pass non-trivial types by const& (or const*) when you only read them — no copy, no mutation. Pass by value only for cheap-to-copy types or when you need an owned copy anyway. (Con.3)
Use constexpr for values computable at compile time — they cost nothing at runtime and can be used in constant contexts (array sizes, template args). (Con.5)
Why: const-correctness is contract documentation the compiler checks — it propagates through call sites and catches accidental mutation at compile time, for free. Source: C++ Core Guidelines (Con).
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 · 135 lines · 3,811 tokens per session scan A f0f2d9c71bc5
cpp 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 3,811 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
secure-dev-c
These rules apply to all C source and header files in the repository and aim to prevent memory corruption, code injection, and unsafe system behavior.
cpp
Cursor rule "cpp" from ItamarZand88/awesome-agent-conventions, covering c++ programming guidelines, basic principles, nomenclature, functions and data.
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.