Borrowing it
Nothing to install: this file belongs to agtm1199/uber-polya. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agtm1199/uber-polya/main/CLAUDE.mdgit clone --depth 1 https://github.com/agtm1199/uber-polyaWrote 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/instructions/agtm1199/uber-polya/claude-md)<a href="https://agentmods.dev/instructions/agtm1199/uber-polya/claude-md"><img src="https://agentmods.dev/badge/instructions/agtm1199/uber-polya/claude-md/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/instructions/agtm1199/uber-polya/claude-md"><img src="https://agentmods.dev/badge/instructions/agtm1199/uber-polya/claude-md.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.01598 | $0.01598 |
| Opus 5.5 | $0.00639 | $0.00639 |
| Sonnet 5.5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
uber-polya CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
uber-polya
Universal problem-solving engine for Claude Code, implementing George Polya's "How to Solve It" methodology as modular skills.
Project Structure
skills/
uber-polya/ -- Orchestrator: chains the full pipeline
uber-model/ -- Phase A: real-world problem → formal mathematical model
references/ -- heuristics, structures, problem-classification, common-mistakes, model-templates
uber-solve/ -- Phase B: formal model → verified solution
references/ -- algorithms, solvers, algorithms-statistics, solvers-statistics, solving-protocols, optimization-hardening
uber-interpret/ -- Phase C: solution → actionable insight
references/ -- interpretation-patterns, visualization
templates/
latex/ -- Jinja2 LaTeX templates + polya.sty style for PDF reports
examples/ -- Worked examples with solver code and visualizations
docs/ -- Architecture, tutorials, contributing guide
How Skills Work
Each skill is a directory under skills/ containing a SKILL.md and a references/ folder. The SKILL.md is loaded when the user invokes /skill-name. Reference files are read on demand (not at invocation) to keep context overhead low.
Conventions
SKILL.md files
- YAML frontmatter with
nameanddescription(description contains trigger phrases) - Structured phases with numbered steps
- Phase gates use
AskUserQuestionfor user confirmation - Self-check lists after each gate
- Reference files are read via explicit
Readtool calls at the specified phase - Keep SKILL.md under 500 lines; move situational content to reference files
Reference files
- Markdown format with consistent heading structure
- Each entry should be self-contained (definition, when to use, example)
- Use tables for quick-lookup content (algorithm selection, chart selection, pattern matching)
- Cross-reference other files by relative path when relevant
Worked examples
- Each example gets its own directory under
examples/ - Required files:
README.md, solver script (Python), sample input/output - Solver scripts use
dataclassforInstanceandSolution, with separatesolve()andverify()functions - Visualization scripts save to PNG (not committed to repo)
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 · 95 lines · 1,598 tokens per session scan A 063abd24334a
uber-polya CLAUDE.md is an instructions file published in the GitHub repository agtm1199/uber-polya (4 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 1,598 tokens to every session, about $0.0064 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.