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/requirements)<a href="https://agentmods.dev/skills/pitimon/8-habit-ai-dev/requirements"><img src="https://agentmods.dev/badge/skills/pitimon/8-habit-ai-dev/requirements.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.02711 |
| Opus 5 | $0.00024 | $0.01355 |
| Sonnet 5 | $0.00010 | $0.00542 |
| Haiku 4.5 | $0.00005 | $0.00271 |
Grade A, and why
requirements 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 8d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 1: Requirements (คิดก่อนทำ)
Habit: H2 — Begin with End in Mind | Anti-pattern: Starting to code without knowing what "done" looks like
Process
-
Choose requirements intake mode: Before drafting the PRD, classify the request as one of two modes and state the mode in the PRD notes.
Mode Use when Discipline Existing-system mode The user is changing, extending, integrating with, or debugging a real codebase, workflow, deployment, or documented system Cite source evidence where available: files, docs, commands, issue links, logs, or user-provided facts. Mark anything not verified from the system as an assumption or open question. Idea-mode The user is shaping a raw product, feature, or system idea before implementation exists Preserve user intent, label assumptions before treating them as constraints, and ask architecture-impacting questions before presenting speculative details as requirements. If the request mixes both, use Existing-system mode for the known system boundary and Idea-mode for new proposed behavior. Do not let proposed behavior masquerade as confirmed system fact.
-
Discover requirements: Before writing EARS criteria, follow the Interview Protocol (loaded below) to discover requirements through structured conversation. Use adaptive depth — Quick (3 questions) for small scope, Standard (5) by default, Deep (7+) for complex features.
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.
- 8d ago First seen · 159 lines · 48 tokens per session scan A b6e9db67663e
requirements 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,711 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.
ship
Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.
sitrep
Situational awareness — where am I, what was I doing, what's next. Context recovery after compression, confusion, or mid-session reorientation.