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/7oSkaaa/polygon-problems-generatorWrote 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/7oskaaa/polygon-problems-generator/00-project)<a href="https://agentmods.dev/rules/7oskaaa/polygon-problems-generator/00-project"><img src="https://agentmods.dev/badge/rules/7oskaaa/polygon-problems-generator/00-project/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/7oskaaa/polygon-problems-generator/00-project"><img src="https://agentmods.dev/badge/rules/7oskaaa/polygon-problems-generator/00-project.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.01267 | $0.01267 |
| Opus 5.5 | $0.00507 | $0.00507 |
| Sonnet 5.5 | $0.00253 | $0.00253 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
00-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- windsurfrules — 95% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared agent context
This is the only copy of roster, layout, pipeline, and critical rules.
Specialist agents (.claude/agents/<role>.md) add only their role contract. Do not paste this file into those stubs — tell the model to Read it.
Deep references (read on demand, do not duplicate):
guidelines.md— full human checklisttutorials/polygon-hints.md— Polygon wording and testlib hintstutorials/<topic>.md— statement / validator / checker / generator / interactordocs/workflow.md— local-first loop and how to prompt a fix
Agent roster
| Agent | Role |
|---|---|
statement-agent |
LaTeX statement + editorial (statement.tex, tutorial.tex) |
validator-agent |
testlib.h input validator (validator.cpp) |
checker-agent |
Standard checker recommendation or custom checker (checker.cpp) |
interactor-agent |
testlib.h interactor for interactive problems (interactor.cpp) |
solutions-agent |
ACC / TLE / WA solutions in C++ and Java |
generator-agent |
testlib.h test generator + FreeMarker script (generator.cpp) |
reviewer-agent |
Full review; blocks on any FAIL verdict |
orchestrator |
Coordinates the pipeline; do not run other agents except through this |
Problem folder layout
problems/<name>/
├── statement/
│ ├── statement.tex
│ └── tutorial.tex
├── solutions/
│ ├── acc.cpp ← main ACC (clear, not over-optimized)
│ ├── acc_java.java
│ ├── acc_alt.cpp ← second ACC, different approach
│ ├── brute.cpp
│ └── wa.cpp
├── generators/
│ └── generator.cpp
├── validator.cpp
├── checker.cpp
└── interactor.cpp ← interactive only
Create with:
mkdir -p problems/<name>/{statement,solutions,generators,samples,validator_tests}
cp templates/validator.cpp problems/<name>/validator.cpp
cp templates/checker.cpp problems/<name>/checker.cpp
cp templates/statement/raw.tex problems/<name>/statement/raw.tex
cp templates/statement/statement.tex problems/<name>/statement/statement.tex
cp templates/statement/tutorial.tex problems/<name>/statement/tutorial.tex
cp templates/generators/generator.cpp problems/<name>/generators/generator.cpp
# interactive only: cp templates/interactor.cpp problems/<name>/interactor.cpp
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 · 117 lines · 1,267 tokens per session scan A ab1de9170288
00-project is a cursor rule published in the GitHub repository 7oSkaaa/polygon-problems-generator (21 stars, last pushed today), licensed MIT. It adds 1,267 tokens to every session, about $0.0051 per session on Opus 5.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
meta-quest-agentic-tools
Use Meta Quest Agentic Tools for Meta Quest and Horizon OS samples.
narrative-writing
A set of rules for writing and editing video-game narratives, connected to a narrative project. It requires the agent to load the project's writing context and story canon, which is the established set of story facts, before making changes.
meta-quest-agentic-tools
Use Meta Quest Agentic Tools for Meta Quest and Horizon OS samples.
visual-and-observational-rules
Defines the visual aspects of the game and how the player observes the world. This includes map color-coding, screen effects, and the overall simulation style.
00-project-overview
Base project rule — purpose, constraints, and defaults for mcp-5etools.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.