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/wangqiqi/cursor-ai-rulesWrote 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/wangqiqi/cursor-ai-rules/c-basics-practices)<a href="https://agentmods.dev/rules/wangqiqi/cursor-ai-rules/c-basics-practices"><img src="https://agentmods.dev/badge/rules/wangqiqi/cursor-ai-rules/c-basics-practices/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/wangqiqi/cursor-ai-rules/c-basics-practices"><img src="https://agentmods.dev/badge/rules/wangqiqi/cursor-ai-rules/c-basics-practices.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.00444 |
| Opus 5.5 | $0.00000 | $0.00178 |
| Sonnet 5.5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
c-basics-practices 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 1mo 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.
What it actually says
C 语言实践 (Practices)
本规则由
@c-basics引用
Makefile
CC = gcc
CFLAGS = -std=c11 -Wall -Wextra -Wpedantic -Werror -O2 -DNDEBUG
SRCS = src/main.c src/core.c src/utils.c
OBJS = $(SRCS:.c=.o)
TARGET = myapp
$(TARGET): $(OBJS)
$(CC) $(OBJS) -o $@ $(LDFLAGS)
.PHONY: all clean test
all: $(TARGET)
clean: rm -f $(OBJS) $(TARGET)
test: ./$(TEST_TARGET)
CMake
cmake_minimum_required(VERSION 3.10)
project(MyProject LANGUAGES C)
set(CMAKE_C_STANDARD 11)
add_compile_options(-Wall -Wextra -Wpedantic -Werror)
add_executable(${PROJECT_NAME} src/main.c src/core.c src/utils.c)
enable_testing()
add_test(NAME unit_tests COMMAND tests)
单元测试框架
#define TEST_CASE(name) static void test_##name(void)
#define RUN_TEST(name) do { printf("Running %s... ", #name); test_##name(); printf("PASSED\n"); } while (0)
#define ASSERT_TRUE(c) do { if (!(c)) { fprintf(stderr, "FAIL: %s:%d\n", __FILE__, __LINE__); exit(1); } } while (0)
#define ASSERT_EQUAL(a, b) ASSERT_TRUE((a) == (b))
原则
- MUST 使用 -Wall -Wextra -Wpedantic
- MUST 为 Release 使用 -O2 -DNDEBUG
- MUST 编写单元测试
引用: @c-basics
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.
- 1mo ago First seen · 61 lines · 0 tokens per session scan A 9cc065825fbf
c-basics-practices is a cursor rule published in the GitHub repository wangqiqi/cursor-ai-rules (16 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 444 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-30.
Other cursor rules, from other repositories
move-copy-semantics
Avoid std::move(const&) silent copies; use sink-by-value + std::move.
vios-error-security
Error handling and security rules for VIOS C++ code.
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.
cpp
Name methods (casing, etc) like "isvalid", "streamtext".
monitor-c-conventions
C coding conventions for HPCPerfStats monitor (C-only).
monitor-c-refactor-standards
Behavior-preserving C refactor standards for HPCPerfStats monitor.