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 skills/7oskaaa/polygon-problems-generator/orchestratornpx skills add 7oSkaaa/polygon-problems-generator --skill orchestratorgit 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/skills/7oskaaa/polygon-problems-generator/orchestrator)<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="Measured on agentmods" 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 | $0.00040 | $0.00347 |
| Opus 5 | $0.00020 | $0.00173 |
| Sonnet 5 | $0.00008 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
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 4d 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
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.
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.
- 4d ago First seen · 31 lines · 40 tokens per session scan A 2caf0e5fd66c
orchestrator is a skill published in the GitHub repository 7oSkaaa/polygon-problems-generator (21 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 347 once invoked, about $0.0002 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.
Other skills, from other repositories
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 "入职".
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…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
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.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).