00-project

A shared rulebook for a project that generates competitive-programming problems for Polygon, including its agents, file layout, workflow, and key constraints.

In plain words
What is it for?
Use it to coordinate statement, validator, checker, interactor, solution, generator, and review agents, while pointing them to detailed references when needed.
Why use it?
It gives the project's specialist agents one consistent source of instructions, reducing conflicting rules and duplicated guidance.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/7oskaaa/polygon-problems-generator/00-project
Clone the repo
git clone --depth 1 https://github.com/7oSkaaa/polygon-problems-generator

Made for: Cursor.

Per session 1,267 This file is loaded in full into every session.
When invoked 1,267 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01267 $0.01267
Opus 5 $0.00633 $0.00633
Sonnet 5 $0.00253 $0.00253
Haiku 4.5 $0.00127 $0.00127

Measured 2d ago against content hash ab1de9170288, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.cursor/rules/00-project.mdc · 117 lines

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 checklist
  • tutorials/polygon-hints.md — Polygon wording and testlib hints
  • tutorials/<topic>.md — statement / validator / checker / generator / interactor
  • docs/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

Read the full file on GitHub · 117 lines

Changes

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.

  1. 2d ago First seen · 117 lines · 1,267 tokens per session scan A ab1de9170288

Subscribe to this mod's changes

00-project is a cursor rule published in the GitHub repository 7oSkaaa/polygon-problems-generator (21 stars, last pushed 2d ago), licensed MIT. It adds 1,267 tokens to every session, about $0.0063 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.