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/isndev/qb-linqWrote 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/isndev/qb-linq/qb-linq-project)<a href="https://agentmods.dev/rules/isndev/qb-linq/qb-linq-project"><img src="https://agentmods.dev/badge/rules/isndev/qb-linq/qb-linq-project.svg" alt="Measured on agentmods" 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.00241 | $0.00241 |
| Opus 5 | $0.00120 | $0.00120 |
| Sonnet 5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
qb-linq-project 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 8d 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
qb-linq (project)
- Library: Header-only C++17,
namespace qb::linq. Public include:<qb/linq.h>only. - Before edits:
AGENTS.md,docs/BUILDING.md(CMake facts),docs/LLM_CONTEXT.md(implementation map). - CRTP: Algorithms live on
detail::query_range_algorithms<Derived, Iter>; implementations callderived().begin()/end(). - Verify: Build
qb_linq_testsand runctestwhen possible; preserveqb_linq_benchmarkbuild if benchmarks touched. User-visible changes:CHANGELOG.md([Unreleased]) perCONTRIBUTING.md. - Scope: Minimal, focused diffs; match surrounding style and Doxygen; do not expand scope beyond the task.
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.
- 8d ago First seen · 13 lines · 241 tokens per session scan A 37604861e49c
qb-linq-project is a cursor rule published in the GitHub repository isndev/qb-linq (13 stars, last pushed 8d ago), licensed MIT. It adds 241 tokens to every session, about $0.0012 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-30.
Other cursor rules, from other repositories
cpp-api-patterns
Result , BSON, and MongoDB C++ API patterns (zero-error).
code-style
Error handling, file organization, security, performance.
uwebsockets
Never use res->onData() without res->onAborted() — the server can crash on client disconnect.
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.
monitor-c-conventions
C coding conventions for HPCPerfStats monitor (C-only).