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.
git clone --depth 1 https://github.com/timurgaleev/vibestackWrote 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/rules/timurgaleev/vibestack/problem-solving)<a href="https://agentmods.dev/rules/timurgaleev/vibestack/problem-solving"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/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/rules/timurgaleev/vibestack/problem-solving"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/problem-solving.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.00848 | $0.00848 |
| Opus 5.5 | $0.00339 | $0.00339 |
| Sonnet 5.5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
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 23d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Solving
The single source for how to approach a problem before and during
implementation. CLAUDE.md carries only the summary.
Think Before Coding
Do not let an assumption pass as fact. Do not hide confusion. Surface trade-offs.
The most common failure is quietly picking one interpretation and running with it. Code built on a wrong assumption is thrown away in full, however much of it there is.
- State assumptions — one line of "proceeding on the assumption that X" is enough.
- Surface multiple readings — if the request is ambiguous, list two or three possible interpretations and ask which one. Do not silently choose.
- Offer the simpler alternative first — say so as soon as you see one. If the user's approach is over-complicated, push back with reasons.
- Stop when confused — "I'll ask if I get stuck partway" is not allowed. Name what is unclear and ask.
Goal-Driven Execution
Convert an imperative instruction into a verifiable exit condition before starting. Only a strong exit condition lets you work independently and judge your own completion.
| Vague instruction | Verifiable goal |
|---|---|
| "fix the bug" | write a test that reproduces it → make it pass → lock it in as a regression test |
| "refactor this" | the same test suite passes before and after |
| "make it faster" | define a measured baseline and a target number → verify by measuring |
| "clean it up" | meets the defined lint / typecheck / coverage bar |
| "make it work" | ask the user what "done" looks like, first |
For multi-step work, state the verification per step — 1. [step] → verify: [how]. A step with no defined verification does not belong in the plan.
The exit condition also names a non-regression boundary: no test deleted, skipped or weakened, and the existing suite still passes.
Status Vocabulary
Report work with exactly one of these states:
| State | Means |
|---|---|
| inspected | read and understood, nothing changed |
| changed locally | edited in the working tree, not yet checked |
| verified locally | the defining check was run here and passed |
| committed | in a local commit |
| pushed | the remote ref moved: HEAD equals git rev-parse origin/<branch> |
| blocked | cannot proceed; name the blocker |
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.
- 23d ago Changed · +19 lines · +157 tokens per session 6351deed5364
- 1mo ago First seen · 74 lines · 691 tokens per session scan A 47afa6f06835
problem-solving is a cursor rule published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 20d ago), licensed MIT. It adds 848 tokens to every session, about $0.0034 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-09-19.
Other cursor rules, from other repositories
minimax-m3-verification
Extended M3 verification playbook: proof selection, multimodal-grounded checks, shell checks, browser checks, and recovery loops.
minimax-m3-self-evolution
MiniMax M3 self-evolution harness: iterative refinement loops, compress-before-iterate, autonomous debugging, and recursive improvement patterns.
composer-debugging
Failing tests, errors, flaky behavior, or a bug with no clear line — reproduce, trace the data, fix the cause, prove it with one scoped test.
520-rule-visibility-system
WHEN command includes "SHOW ACTIVE RULES" or "DEBUG RULES" ENSURE providing visibility and debugging tools for the rule system.
500-rule-debugging
description: WHEN command includes "SHOW ACTIVE RULES" or "DEBUG RULES" ENSURE displaying visible rule information globs: ["/.md", "/.mdc", "/.{js,ts,jsx,tsx,py}"] alwaysApply: true.
performance
Performance: profiling-first optimization, caching, bottleneck patterns.