polygon-problems-generator: Skill for Claude Code

.agents/skills/orchestrator/SKILL.md

orchestrator is a skill for Claude Code, Codex from 7oSkaaa/polygon-problems-generator. It costs 40 tokens per session (347 once invoked), scanned A, original, MIT.

A coordinator for creating and maintaining competitive-programming problems and their supporting files.

In plain words
What is it for?
Starting or continuing problem creation, refining individual components, managing the problem folder, and rerunning failed parts of the workflow.
Why use it?
It organizes the work across statements, validators, checkers, solutions, generators, and reviews so components remain consistent.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents; installed under .agents/ (shared by several agents).

This is 7oSkaaa/polygon-problems-generator's own configuration. It tells Claude Code and Codex how to work on polygon-problems-generator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything polygon-problems-generator configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 7oSkaaa/polygon-problems-generator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/7oSkaaa/polygon-problems-generator/main/.agents/skills/orchestrator/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/7oSkaaa/polygon-problems-generator

Made for: Claude Code, Codex.

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

agentmods badge for orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/7oskaaa/polygon-problems-generator/orchestrator/github.svg)](https://agentmods.dev/skills/7oskaaa/polygon-problems-generator/orchestrator)
Your own site
<a href="https://agentmods.dev/skills/7oskaaa/polygon-problems-generator/orchestrator"><img src="https://agentmods.dev/badge/skills/7oskaaa/polygon-problems-generator/orchestrator/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.

agentmods 80×15 button for orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/7oskaaa/polygon-problems-generator/orchestrator"><img src="https://agentmods.dev/badge/skills/7oskaaa/polygon-problems-generator/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 347 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00040 $0.00347
Opus 5.5 $0.00016 $0.00139
Sonnet 5.5 $0.00008 $0.00069
Haiku 4.5 $0.00004 $0.00035

Measured 2mo ago against content hash 2caf0e5fd66c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orchestrator 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 2mo 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.

.agents/skills/orchestrator/SKILL.md · 31 lines

What it actually says

Read .claude/shared.md first.

You are the Problem Generator Orchestrator.

Shared: Read .claude/shared.md first (roster, layout, pipeline, critical rules). Open guidelines.md only if you need the long checklist.

Spawning Sub-Agents

Use the Agent tool with the matching subagent_type. Pass problem description, constraints, existing content (when refining), feedback, multitest, interactive, and tell the sub-agent to follow .claude/shared.md.

Task subagent_type
Generate or refine statement / tutorial statement-agent
Generate or refine validator validator-agent
Recommend or generate checker checker-agent
Suggest approach or generate solution solutions-agent
Generate generator or stress script generator-agent
Generate interactor (interactive only) interactor-agent
Review component or full problem reviewer-agent

Follow the Pipeline in .claude/shared.md. Write each file as soon as it is generated. On FAIL or verify.sh failure, regenerate only that component (/fix-component).

Decide multitest and interactive once (see shared.md) and pass them to every sub-agent.

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. 2mo ago First seen · 31 lines · 40 tokens per session scan A 2caf0e5fd66c

Subscribe to this mod's changes

orchestrator is a skill published in the GitHub repository 7oSkaaa/polygon-problems-generator (21 stars, last pushed 11d ago), licensed MIT. It adds 40 tokens to every session and 347 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

repovive-contest-dev

Production contest development on Repovive, end to end, through the repovive-mcp server. Use for authoring real, publishable competitive-programming problems and full rounds: designing a difficulty curve, writing rigorous statements, building generators and validators, producing test data strong enough to kill wrong…

dwin-gharibi/repovive-mcp · 162 tokens

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

book-mirror

Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…

garrytan/gbrain · 138 tokens

exam-forecast

Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.

anthropics/claude-for-legal · 73 tokens

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

companion-inc/feynman · 63 tokens

deck-course-module

A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.

nexu-io/html-anything · 25 tokens