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/AhmedAbouelkher/micro_marketWrote 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/ahmedabouelkher/micro_market/recommended-c-style-and-coding-rules)<a href="https://agentmods.dev/rules/ahmedabouelkher/micro_market/recommended-c-style-and-coding-rules"><img src="https://agentmods.dev/badge/rules/ahmedabouelkher/micro_market/recommended-c-style-and-coding-rules/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/ahmedabouelkher/micro_market/recommended-c-style-and-coding-rules"><img src="https://agentmods.dev/badge/rules/ahmedabouelkher/micro_market/recommended-c-style-and-coding-rules.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.09238 |
| Opus 5 | $0.00000 | $0.04619 |
| Sonnet 5 | $0.00000 | $0.01848 |
| Haiku 4.5 | $0.00000 | $0.00924 |
Grade A, and why
Recommended-C-style-and-coding-rules 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 1,362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Table of Contents
- Recommended C style and coding rules
- Table of Contents
- The single most important rule
- Integration with VSCode
- Conventions used
- General rules
- Comments
- Functions
- Variables
- Structures, enumerations, typedefs
- Compound statements
- Macros and preprocessor directives
- Documentation
- Header/source files
- Clang format integration
- Artistic style configuration
- Eclipse formatter
The single most important rule
Let's start with the quote from GNOME developer site.
The single most important rule when writing code is this: check the surrounding code and try to imitate it.
As a maintainer it is dismaying to receive a patch that is obviously in a different coding style to the surrounding code. This is disrespectful, like someone tromping into a spotlessly-clean house with muddy shoes.
So, whatever this document recommends, if there is already written code and you are patching it, keep its current style consistent even if it is not your favorite style.
Integration with VSCode
VScode comes with pre-installed clang-format tool (part of LLVM package) that has been design to help developers with auto-format tool during code development.
As such, it allows users to format code on file change (and save).
When file is saved, vscode will try to invoke the clang-format and format the code. Rules to use are in .clang-format file. If clang-format cannot find the rules in the path of current file, it will go all the way up to the root, until one is found. If still none is available, default rules are then being used.
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.
- 10d ago First seen · 1,362 lines · 9,238 tokens per session scan A acdabf71fa6d
Recommended-C-style-and-coding-rules is a cursor rule published in the GitHub repository AhmedAbouelkher/micro_market (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,238 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-08-31.
Other cursor rules, from other repositories
move-copy-semantics
Avoid std::move(const&) silent copies; use sink-by-value + std::move.
cuda
Definitive guidelines for writing high-performance, maintainable, and error-resistant CUDA C++ code, focusing on modern practices, memory management, kernel optimization, and robust error handling.
vios-error-security
Error handling and security rules for VIOS C++ code.
qb-linq-project
qb-linq — header-only C++17 LINQ; read AGENTS.md and docs/LLMCONTEXT.md before editing.
monitor-c-conventions
C coding conventions for HPCPerfStats monitor (C-only).
monitor-c-refactor-standards
Behavior-preserving C refactor standards for HPCPerfStats monitor.