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 lucastamoios/skills --skill think-throughgit clone --depth 1 https://github.com/lucastamoios/skillsWrote 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/lucastamoios/skills/think-through)<a href="https://agentmods.dev/skills/lucastamoios/skills/think-through"><img src="https://agentmods.dev/badge/skills/lucastamoios/skills/think-through/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/lucastamoios/skills/think-through"><img src="https://agentmods.dev/badge/skills/lucastamoios/skills/think-through.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.00052 | $0.01471 |
| Opus 5 | $0.00026 | $0.00736 |
| Sonnet 5 | $0.00010 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
think-through 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 10d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Think Through
This skill helps you reason through a design decision that feels uncertain, off, or underexplored. It is not brainstorming (that's divergent). It is not requirements gathering (that's about what). It is structured convergent thinking about a specific choice and its consequences.
Use it when you have a gut feeling something is wrong but cannot articulate why, or when two valid options seem equivalent but you suspect they are not.
Argument: $ARGUMENTS
When to use this skill
- "Something feels off about this design but I can't say what"
- "We have two options and I don't know which is better"
- "This works but I'm worried about edge cases I haven't thought of"
- "Is this the right abstraction / key / boundary / name?"
Process
Work through these steps in order. Each step is its own message - do not combine them. Wait for the user's reaction before moving to the next step.
Step 1: Frame the decision
State the decision clearly in one sentence. Then state the two (or more) options being considered. If the user gave a vague "something feels off," help them articulate what the actual decision point is.
Format:
Decision:
Option A: Option B: (more if needed)
Current leaning: <which option and why, or "unsure">
Read relevant code, docs, and requirements to ground the framing in reality. Do not frame based on assumptions - verify what actually exists.
Step 2: Three-property test (if the decision involves identity, keys, or dedup)
If the decision involves choosing what goes into an identifier, key, or dedup mechanism, run the three-property test:
| Property | Definition | Option A | Option B |
|---|---|---|---|
| Deterministic | Same logical input always produces the same key | ? | ? |
| Unique | Different logical events produce different keys | ? | ? |
| Stable | Retries of the same event do not change the key | ? | ? |
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.
- 10d ago First seen · 134 lines · 52 tokens per session scan A 10de73d2b0be
think-through is a skill published in the GitHub repository lucastamoios/skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,471 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…