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 skills add tamnguyendinh/Anvien --skill problem-solvinggit clone --depth 1 https://github.com/tamnguyendinh/AnvienWrote 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/tamnguyendinh/anvien/problem-solving)<a href="https://agentmods.dev/skills/tamnguyendinh/anvien/problem-solving"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/problem-solving/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/skills/tamnguyendinh/anvien/problem-solving"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/problem-solving.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00880 |
| Opus 5 | $0.00016 | $0.00440 |
| Sonnet 5 | $0.00006 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
problem-solving 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 9d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem-Solving Techniques
A structured toolkit of high-leverage cognitive and architectural techniques to break through stuck points, eliminate spiraling complexity, and discover elegant solutions.
Core Philosophy
"One powerful abstraction > ten clever hacks"
Rather than managing complexity through brute force, these techniques help you uncover the fundamental principles that make complexity unnecessary.
Symptom Matcher & Dispatch Table
When encountering a difficult technical problem or blocker, match your symptom to the appropriate technique:
| Symptom / How You're Stuck | Recommended Technique | Target Reference |
|---|---|---|
| Unsure which method to apply | Stuck-Type Diagnostic Dispatch | references/when-stuck-dispatch.md |
| Complexity spiraling / Same logic 5+ ways | Simplification Cascades | references/simplification-cascades.md |
| Conventional solutions inadequate / Need innovation | Collision-Zone Thinking | references/collision-zone-thinking.md |
| Rigid assumptions / "Only one way" mindset | Inversion Exercise | references/inversion-exercise.md |
| Recurring pattern across 3+ domains | Meta-Pattern Recognition | references/meta-pattern-recognition.md |
| Uncertain about production limits & extreme load | Scale Game | references/scale-game.md |
Problem-Solving Workflow
[Technical Blocker / Stuck Point]
│
▼
[Identify Stuck Symptom]
│
┌───────────────────────┼───────────────────────┐
│ │ │
▼ ▼ ▼
[Complexity Spiraling] [Need Breakthrough] [Rigid Assumptions]
references/simplification- references/collision- references/inversion-
cascades.md zone-thinking.md exercise.md
│ │ │
├───────────────────────┼───────────────────────┤
│ │ │
▼ ▼ ▼
[Recurring Pattern] [Extreme Scale Limits] [Unsure Where to Start]
references/meta-pattern- references/scale- references/when-stuck-
recognition.md game.md dispatch.md
│
▼
[Apply Technique & Extract Invariant]
│
▼
[Synthesize Clean Architectural Solution]
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 84 lines · 32 tokens per session scan A ee586ad3f229
problem-solving is a skill published in the GitHub repository tamnguyendinh/Anvien (9 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 880 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-09-03.
Other skills, from other repositories
slides
A slide generator that creates PNG images for presentation decks, including simple backgrounds for spoken-video scripts and fuller layouts for standalone presentations.
idea-team
A structured group discussion for exploring a product idea through three roles: researcher, critic, and analogy finder. The roles look for evidence, weaknesses, and useful comparisons.
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.
typescript-project
Modern TypeScript project architecture guide for 2025. Use when creating new TS projects, setting up configurations, or designing project structure. Covers tech stack selection, layered architecture, and best practices.
zig-project
Modern Zig project architecture guide. Use when creating Zig projects (systems programming, CLI tools, game dev, high-performance services). Covers explicit allocators, comptime, error handling, and build system.
architecture-foundation
Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before…