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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/agtm1199/uber-polya/agents-md"><img src="https://agentmods.dev/badge/instructions/agtm1199/uber-polya/agents-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/agents-md"><img src="https://agentmods.dev/badge/instructions/agtm1199/uber-polya/agents-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.01179 | $0.01179 |
| Opus 5.5 | $0.00472 | $0.00472 |
| Sonnet 5.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 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 — 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.
- 1mo 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 8mo ago), licensed Apache-2.0. It adds 1,179 tokens to every session, about $0.0047 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.