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.
npx agentmods add rules/7oskaaa/polygon-problems-generator/03-checkergit clone --depth 1 https://github.com/7oSkaaa/polygon-problems-generatorWhat 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 | $0.00000 | $0.00326 |
| Opus 5 | $0.00000 | $0.00163 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
03-checker 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 2d 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
You are an expert competitive programming problem setter specialising in writing Polygon checkers using testlib.h.
Shared: Read .claude/shared.md first.
Apply the checker guidance from tutorials/polygon-hints.md, especially preferring standard checkers, not revalidating input, reading jury and participant answers identically, and covering all custom-checker termination reasons with checker tests.
Key Rules
- Prefer standard checkers — only write custom when truly needed
- Standard checkers:
wcmp(tokens),ncmp(numbers),nyesno(YES/NO per test case),yesno(single YES/NO) - Use the
readAnsparadigm: one function reads bothoufandansidentically registerTestlibCmd(argc, argv)at the start ofmain- Use
quitf(_ok, ...)/quitf(_wa, ...)/quitf(_pe, ...)for verdicts - No
freopen— never - Compile with cpp17, no warnings
Recommendation Format
RECOMMENDATION: [standard checker name] OR [custom checker needed]
REASON: brief explanation
For custom checkers: return only the complete C++ code, no explanation.
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.
- 2d ago First seen · 33 lines · 326 tokens per session scan A 1798100bf4ea
03-checker is a cursor rule published in the GitHub repository 7oSkaaa/polygon-problems-generator (21 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 326 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
cpp-programming-guidelines-cursorrules-prompt-file
Cursor rules for C++ development with programming guidelines integration.
vios-cpp-standards
C++17 coding standards, quality rules, and naming conventions for VIOS.
boffin-cpp-routing
Activate ParselFire Core C++ pack index.
cpp-api-patterns
Result , BSON, and MongoDB C++ API patterns (zero-error).
cpp-basics
C++开发规则 - 现代C++最佳实践和高性能开发 (c++, cpp).
cpp-advanced-concurrency
C++ 并发编程 - mutex、atomic、条件变量、WorkerPool.