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 instructions/agtm1199/uber-polya/agents-mdgit clone --depth 1 https://github.com/agtm1199/uber-polyaWhat 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.01179 | $0.01179 |
| Opus 5 | $0.00589 | $0.00589 |
| Sonnet 5 | $0.00236 | $0.00236 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
uber-polya AGENTS.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 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
uber-polya
Universal problem-solving engine implementing George Polya's "How to Solve It" methodology. Turns real-world problems into mathematically verified solutions with actionable insights.
What This Does
uber-polya solves problems through a three-phase pipeline:
- Model (Phase A): Translate the real-world problem into a formal mathematical model using Socratic dialogue, 91 mathematical structures, and 17 Polya heuristics.
- Solve (Phase B): Select the right algorithm from 305 cataloged algorithms, implement a verified Python solver, and prove correctness.
- Interpret (Phase C): Translate the solution back into real-world meaning with sensitivity analysis, visualizations, and actionable recommendations.
How to Use
When a user presents a problem to solve, follow the full protocol in docs/methodology.md. That document contains:
- Step-by-step instructions for each phase
- Structured artifact schemas (Formal Model, Solution Report, Interpretation Report)
- Reference file paths and when to consult them
- Self-checks, error recovery, and fast-track shortcuts
- Python solver coding conventions
Quick Start
- Classify the problem: Is it a problem to Find or to Prove?
- Consult
skills/uber-model/references/problem-classification.mdfor rapid pattern matching - Follow Phase A → Phase B → Phase C as documented in
docs/methodology.md - At each phase gate, present your work and ask the user to confirm before proceeding
Project Structure
skills/
uber-polya/ Orchestrator: chains the full pipeline
uber-model/ Phase A: real-world problem → formal model
references/ Heuristics, structures, problem classification, common mistakes
uber-solve/ Phase B: formal model → verified solution
references/ 305 algorithms, 26 solver libraries, solving protocols
uber-interpret/ Phase C: solution → actionable insight
references/ Interpretation patterns, 37+ visualization templates
templates/
latex/ Jinja2 LaTeX templates + polya.sty for PDF reports
examples/ 36 worked examples with runnable Python solvers
docs/
methodology.md Full tool-agnostic protocol (start here)
architecture.md System design and expansion patterns
creating-skills.md How to build custom skills
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.
- 2d ago First seen · 98 lines · 1,179 tokens per session scan A c6a17834954c
uber-polya AGENTS.md is an instructions file published in the GitHub repository agtm1199/uber-polya (4 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 1,179 tokens to every session, about $0.0059 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-31.
Other instructions, from other repositories
PPT-Design-Skill CLAUDE.md
Instructions for sunchaokun/PPT-Design-Skill: Use the ppt-design-skill workflow for presentation design tasks. The published pptx-designer Python library creates the editable PPTX; this repository owns the design process, installation, rendering, and PNG review.
arkgum-agent-skills AGENTS.md
Instructions for arkgum/arkgum-agent-skills, covering repository instructions, skill contract, public-safety contract and repository maintenance.
agent-skills CLAUDE.md
Claude Code instructions for motherduckdb/agent-skills, covering motherduck skills -- claude code context, what motherduck is, default routing, install notes and non-negotiable rules.
agent-skills GEMINI.md
Gemini CLI instructions for motherduckdb/agent-skills, covering motherduck skills for gemini cli, default routing, skill catalog, utility and workflow.
project-scaffold-setup-skills AGENTS.md
Instructions for Victory-7291/project-scaffold-setup-skills, covering agents.md, 工作范围, 维护规则, 文档风格 and 新增或修改 skill 的检查清单.
kortex CLAUDE.md
Instructions for Heapy/kortex, a project described as: Agent Skills for Kotlin Development.