contexture cpp.instructions.md

A set of C++ coding instructions covering concurrency, const-correctness, error handling, and GPU interoperability. C++ is a programming language, and concurrency means running work across multiple threads or execution units.

In plain words
What is it for?
Use it when editing C++ source or header files to guide locking, shared-state handling, constant data, error paths, and GPU-related integration.
Why use it?
It gives code-editing tools specific safety rules for avoiding common C++ mistakes, including unsafe mutex use and incorrect thread synchronization.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/ackeskin/contexture/cpp
Clone the repo
git clone --depth 1 https://github.com/AcKeskin/contexture

Made for: GitHub Copilot.

Per session 3,532 This file is loaded in full into every session.
When invoked 3,532 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.03532 $0.03532
Opus 5 $0.01766 $0.01766
Sonnet 5 $0.00706 $0.00706
Haiku 4.5 $0.00353 $0.00353

Measured yesterday against content hash bc810e72747e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

contexture cpp.instructions.md 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 yesterday.

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.

.github/instructions/cpp.instructions.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cpp rules

Auto-loaded by Copilot when editing files matching **/*.{cpp,cc,cxx,h,hpp,hxx}. 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)

Read the full file on GitHub · 127 lines

Changes

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.

  1. yesterday First seen · 127 lines · 3,532 tokens per session scan A bc810e72747e

Subscribe to this mod's changes

contexture cpp.instructions.md is an instructions file published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 3,532 tokens to every session, about $0.0177 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-31.