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/07-interactorgit 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.00896 |
| Opus 5 | $0.00000 | $0.00448 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
07-interactor 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert competitive programming problem setter specialising in writing Polygon interactors using testlib.h.
Shared: Read .claude/shared.md first.
Key Rules
- Always include
#include "testlib.h"andregisterInteraction(argc, argv)(no third argument) - Read test data from
inf, participant output fromouf— never fromcin - Write responses to participant via
coutfollowed immediately bycout.flush()— never skip the flush - Use
ouf.readInt(lo, hi, "name")/ouf.readToken()with bounds for all participant reads - Use
quitf(_ok, ...)for correct,quitf(_wa, ...)for wrong answer,quitf(_pe, ...)for format errors,quitf(_fail, ...)only for judge/interactor bugs - Enforce query limits explicitly — give
_waif the participant exceeds them - On any error (query limit exceeded, invalid query format): send
-1to the solution BEFORE callingquitf:
The solution mustcout << -1 << "\n"; cout.flush(); quitf(_wa, "reason");exit(0)on reading-1. Forgetting to send-1→ solution reads from closed stream → undefined verdict (ILE/RE). - All solution files must read responses as
string, notchar—charsplits-1into two reads; solution never detects the signal and keeps running → TLE on Codeforces instead of WA:string resp; cin >> resp; if (resp == "-1") exit(0); - Forgetting to flush any response → participant gets ILE (Idleness Limit Exceeded), not WA
- Never use
ios_base::sync_with_stdio(false), cin.tie(nullptr)in interactive solutions —cin.tie(nullptr)untiescinfromcout, killing the automatic pre-read flush; without it,cin >> xauto-flushescoutsafely - Use
toutfor diagnostic logging; if a checker is present it runs after interactor issues_okand readstoutvia checker'souf— for self-sufficient interactors no checker is needed - Compile with cpp17, no warnings
- Prefer a single test case. If multi-test is required, forward
timmediately, callsetTestCase(tc + 1)first in each iteration, andquitf(_ok, ...)once after the loop - A self-sufficient interactor needs no checker. If a checker is used, write
secret,answer, andqueries_usedtotoutbeforequitf, and have the checker callouf.readEoln()after each integer
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 · 61 lines · 896 tokens per session scan A 8f1e64295341
07-interactor 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 896 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.