Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pitimon/8-habit-ai-dev/plugin install 8-habit-ai-devWrote 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/pitimon/8-habit-ai-dev/research)<a href="https://agentmods.dev/skills/pitimon/8-habit-ai-dev/research"><img src="https://agentmods.dev/badge/skills/pitimon/8-habit-ai-dev/research.svg" alt="Measured on agentmods" 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.00048 | $0.02359 |
| Opus 5 | $0.00024 | $0.01179 |
| Sonnet 5 | $0.00010 | $0.00472 |
| Haiku 4.5 | $0.00005 | $0.00236 |
Grade A, and why
research 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 6d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 0: Research (ศึกษาก่อนกำหนด)
Habit: H5 — Seek First to Understand | Anti-pattern: Defining requirements without investigating the problem space
Before You Start: Is the Problem Statement Fuzzy?
/research is convergent — it assumes you know what to investigate and produces a research brief with verified sources. If the problem statement itself is still fuzzy (you're not sure what you're really solving, stakeholders disagree, the request is vague), do not start here. Invoke superpowers:brainstorming from the claude-plugins-official:superpowers plugin first — it ships a hard-gate collaborative design session that produces a committed spec document before any research. Come back to /research once the problem is crisp.
If you don't have Superpowers installed, proceed here only when the problem is clearly stated — otherwise you risk producing excellent research on the wrong problem. (v2.4.1 removed our own /brainstorm skill in favor of Superpowers' stronger equivalent — see ADR-006.)
Research Depth
Choose the appropriate depth based on the problem complexity. Default is Standard.
| Depth | When to Use | Tools | Verification |
|---|---|---|---|
| Quick | Codebase-only question; "how does X work here?" | Read, Glob, Grep | Self-verify file paths |
| Standard | Default — investigate problem space with codebase + external sources | + WebSearch, WebFetch | Self-verify all sources |
| Deep | High-stakes decision; multi-option evaluation; unfamiliar domain | + Agent (research-verifier) | Agent-verified sources |
Auto-detection: If the user provides no depth keyword, select based on the argument:
- Single codebase question → Quick
- General problem investigation → Standard
- "compare", "evaluate", "which should we", or 3+ options mentioned → Deep
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.
- 6d ago First seen · 197 lines · 48 tokens per session scan A b400edad55b2
research is a skill published in the GitHub repository pitimon/8-habit-ai-dev (3 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 2,359 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-08-31.
Other skills, from other repositories
brainstorm
Interactive idea maturation — explore, research, shape raw ideas into actionable plans. Use when you have a rough idea and want to think it through.
challenge
Adversarial review — Fable 5 stress-tests reasoning, Gemini checks knowledge. Use before plan or architecture decisions.
review
Business review — weekly health check, monthly close, or ad-hoc audit. Subcommands: weekly, monthly, check. Use for periodic reviews or metrics assessment.
nextjs-patterns
Next.js App Router — Server Components, Actions, streaming, caching. Use when building or migrating Next.js apps.
sitrep
Situational awareness — where am I, what was I doing, what's next. Context recovery after compression, confusion, or mid-session reorientation.
fastapi
FastAPI best practices + Pydantic. Use when building or reviewing FastAPI APIs.