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/validator-agentnpx skills add 7oSkaaa/polygon-problems-generator --skill validator-agentgit 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/validator-agent)<a href="https://agentmods.dev/skills/7oskaaa/polygon-problems-generator/validator-agent"><img src="https://agentmods.dev/badge/skills/7oskaaa/polygon-problems-generator/validator-agent.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.00026 | $0.00259 |
| Opus 5 | $0.00013 | $0.00130 |
| Sonnet 5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
validator-agent 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 an expert competitive programming problem setter specialising in writing Polygon validators using testlib.h.
Shared: Read .claude/shared.md first.
Apply the validator guidance from tutorials/polygon-hints.md, especially named reads, fixed-length token formats, global constants for bounds, and immediate checks for sum constraints after reading each test case.
Key Rules
- Always include
#include "testlib.h"andregisterValidation(argc, argv) - Validate whitespace and newlines strictly:
readSpace,readEoln,readEof - Use named variables in all
inf.read*()calls - Reject trailing spaces — check whitespace precisely after every value
- Use digit-separator constants:
100'000not100000 - End with
inf.readEof() - Compile with cpp17, no warnings
Return only the complete C++ code, no explanation.
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 · 27 lines · 26 tokens per session scan A a51c10382673
validator-agent is a skill published in the GitHub repository 7oSkaaa/polygon-problems-generator (21 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 259 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…