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 vibeeval/vibecosystem --skill cognitive-modesgit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/cognitive-modes)<a href="https://agentmods.dev/skills/vibeeval/vibecosystem/cognitive-modes"><img src="https://agentmods.dev/badge/skills/vibeeval/vibecosystem/cognitive-modes/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/vibeeval/vibecosystem/cognitive-modes"><img src="https://agentmods.dev/badge/skills/vibeeval/vibecosystem/cognitive-modes.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.00073 | $0.01995 |
| Opus 5 | $0.00036 | $0.00997 |
| Sonnet 5 | $0.00015 | $0.00399 |
| Haiku 4.5 | $0.00007 | $0.00199 |
Grade A, and why
cognitive-modes 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 5d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cognitive Modes
Her gorev ayni dusunme sekli gerektirmez. Mimari karar icin derin analiz, hotfix icin hizli aksiyon, bug icin sistematik izleme gerekir. Yanlis mod = yanlis sonuc.
5 Dusunme Modu
1. ANALYTICAL (Derin Analiz)
NE ZAMAN: Mimari karar, teknoloji secimi, trade-off analizi
NASIL: Birden fazla perspektif, artilari/eksileri, uzun vadeli etki
HIZI: Yavas ama kapsamli
TOKEN: Yuksek (derinlemesine dusunme)
Davranis:
- Her secenegi en az 3 acidan degerlendir
- Uzun vadeli sonuclari dusun (6 ay, 1 yil)
- "Neden" sorusunu en az 3 kez sor (5 Whys)
- Karar oncesi risk analizi yap
- Alternatif yaklasimlari listele
Ornek gorevler:
- "Monolith mi microservice mi?"
- "Hangi database kullanmaliyiz?"
- "Auth sistemi nasil tasarlanmali?"
- "Bu refactoring yapilmali mi?"
Prompt pattern:
Bu karari ANALYTICAL modda degerlendir:
1. En az 3 secenek belirle
2. Her secenegin 3+ artisi ve 3+ eksisini listele
3. Uzun vadeli etkileri degerlendir
4. Risk analizi yap
5. Net oneri ver (nedenle birlikte)
2. CREATIVE (Yaratici Cozum)
NE ZAMAN: Yeni feature tasarimi, UX/UI, problem cozme, naming
NASIL: Sinir koymadan dusun, sonra daralt
HIZI: Orta
TOKEN: Orta
Davranis:
- Ilk 5 fikri YARGILAMA, sadece uret
- Farkli alanlardan analoji kullan
- "Ya su olsa?" sorusu sor
- Kisitlamalari gec, sonra geri getir
- En iyi 2-3 fikri secip detaylandir
Ornek gorevler:
- "Bu feature'i nasil tasarlayalim?"
- "Kullanici deneyimini nasil iyilestirelim?"
- "Bu API'nin ismi ne olmali?"
- "Onboarding akisi nasil olmali?"
Prompt pattern:
Bu gorevi CREATIVE modda ele al:
1. En az 5 farkli yaklasim uret (yargilama)
2. Her birini tek cumlede acikla
3. En ilginc 2-3'unu sec
4. Secilenleri detaylandir
5. Final oneri ver
3. SYSTEMATIC (Adim Adim)
NE ZAMAN: Implementation, migration, setup, deployment
NASIL: Sira onemli, her adim dogrulanmali
HIZI: Orta-yavas
TOKEN: Orta
Davranis:
- Gorevi numarali adimlara bol
- Her adimi tamamla, SONRA sonrakine gec
- Her adim sonrasi dogrulama yap
- Adimlar arasi bagimliliklari belirle
- Hata durumunda hangi adima donulecegini belirt
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.
- 5d ago First seen · 229 lines · 73 tokens per session scan A 56b94be7cef9
cognitive-modes is a skill published in the GitHub repository vibeeval/vibecosystem (529 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,995 once invoked, about $0.0004 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
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
hive.error-recovery
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.