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/AdobeDocs/ff-services-docsWrote 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/adobedocs/ff-services-docs/security-lang-c)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/security-lang-c"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/security-lang-c/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/adobedocs/ff-services-docs/security-lang-c"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/security-lang-c.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.00497 | $0.00497 |
| Opus 5.5 | $0.00199 | $0.00199 |
| Sonnet 5.5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
security-lang-c 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.
This is a copy
100% identical to secure-dev-c — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: globs: /*.c,/*.h alwaysApply: false
Secure C Development
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.
All violations must include a clear explanation of which rule was triggered and why, to help developers understand and fix the issue effectively.
Generated code must not violate these rules. If a rule is violated, a comment must be added explaining the issue and suggesting a correction.
1. Avoid Unsafe Functions
- Rule: Do not use functions like
gets,strcpy,sprintf, orscanfwith%s. Use bounded or safer alternatives likefgets,strncpy, orsnprintf.
2. Always Validate Input Lengths
- Rule: Validate the length of user or external input before copying, storing, or processing it to prevent buffer overflows.
3. Initialize All Pointers and Memory
- Rule: All pointers and allocated memory must be explicitly initialized before use.
4. Check All Memory Allocations
- Rule: Check the result of
malloc,calloc, orreallocforNULLbefore using the returned pointer.
5. Avoid Format String Vulnerabilities
- Rule: Never pass user-controlled strings directly as the format argument to functions like
printf,fprintf, orsyslog.
6. Free All Allocated Memory
- Rule: All dynamic memory must be properly freed to avoid memory leaks. Avoid double-free and use-after-free errors.
7. Do Not Trust Environment Variables
- Rule: Environment variables must not be used directly in sensitive operations like file access, exec calls, or security checks without validation.
8. Avoid System and Shell Calls with Input
- Rule: Do not use
system(),popen(), or similar functions with user-controlled input. Use direct APIs when possible.
9. Limit Pointer Arithmetic and Casting
- Rule: Avoid unnecessary pointer arithmetic and type casting that can bypass bounds or type safety.
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 · 43 lines · 497 tokens per session scan A 96c7a93ca810
security-lang-c is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 497 tokens to every session, about $0.0020 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to secure-dev-c, differing in 0 lines, and is treated as a copy.
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.