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 orlando-japan/claude-code-setting --skill think-before-codinggit clone --depth 1 https://github.com/orlando-japan/claude-code-settingWrote 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/orlando-japan/claude-code-setting/think-before-coding)<a href="https://agentmods.dev/skills/orlando-japan/claude-code-setting/think-before-coding"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/think-before-coding/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/orlando-japan/claude-code-setting/think-before-coding"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/think-before-coding.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.00036 | $0.00477 |
| Opus 5.5 | $0.00014 | $0.00191 |
| Sonnet 5.5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
think-before-coding 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 1mo 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.
What it actually says
Think before coding
Most bad AI code comes from confidently building on a wrong assumption. This skill forces assumptions above the waterline before code hits the editor.
When to use
- Starting any task touching more than ~3 files.
- Whenever an existing function or API is central to what you're about to do.
- After receiving a vague bug report.
Protocol
Step 1 — draft the assumption list. Write out (in chat, not comments) every claim your planned change depends on. Aim for 5–15 items. Categories:
- Input shape ("the
userobject has apermissionsarray") - API behavior ("
fetch()throws on 4xx") - Invariant ("this function is only called after auth")
- Edge case absence ("the list is never empty")
- Type narrowing ("
valueisstringhere, notstring | null")
Step 2 — classify each assumption.
- Obvious (the types or local code make it unambiguous) → skip.
- Load-bearing and uncertain → verify by reading the relevant source, running the code, or checking docs. Spend up to ~10 minutes per assumption. If you can't resolve it, ask the user.
- Cosmetic (wrong guess wouldn't break correctness) → note it and continue.
Step 3 — act on what you learned. If verification changed the design, revise the plan before writing code. Don't patch the wrong plan after the fact.
Anti-patterns
- "I'll check it in the tests." Tests find bugs after you've built on them. Check first.
- "Most likely it's X." Probabilistic reasoning is fine for priors, not load-bearing code.
- Skipping the list because the task is "simple." Simple tasks with one wrong assumption produce subtle bugs.
Output
A short pre-code section labelled "Assumptions" with the list and how you verified each, before any code edits.
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.
- 1mo ago First seen · 47 lines · 36 tokens per session scan A 97c4bf8bb764
think-before-coding is a skill published in the GitHub repository orlando-japan/claude-code-setting (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 477 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
react-grab
Use when the user wants a hands-free loop where grabbing UI elements in the browser with React Grab feeds tasks to the agent automatically, with no copy-paste or manual handoff. Triggers: "watch react grab", "monitor my grabs", "auto-process react grab", "watch my clipboard for grabs". Not for a one-off paste of a…
output-standards
Use this skill when defining or enforcing output formatting standards for agent responses in WrongStack. Triggers: user says "next steps format", "output standard", "response format", "final message format", "standardize next steps".
web-platform-baseline
Use this skill before asserting that a CSS, HTML or accessibility capability is available, unavailable, or the right tool — it carries dated, refreshable platform facts and refuses to let stale knowledge be stated as current. Triggers: user says "container query", "can I use", "browser support", "modern CSS", ":has"…
doc-coauthoring
Collaboratively author technical specifications, RFCs, PRDs, ADRs, and decision documents through structured context gathering, iterative refinement, and blind reader testing. Use when drafting substantial documentation, architecture proposals, or engineering design records.