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 ChrisLamDev/hermes-core-skills --skill think-toolgit clone --depth 1 https://github.com/ChrisLamDev/hermes-core-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/chrislamdev/hermes-core-skills/think-tool)<a href="https://agentmods.dev/skills/chrislamdev/hermes-core-skills/think-tool"><img src="https://agentmods.dev/badge/skills/chrislamdev/hermes-core-skills/think-tool.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.00054 | $0.01557 |
| Opus 5 | $0.00027 | $0.00779 |
| Sonnet 5 | $0.00011 | $0.00311 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade C, and why
think-tool scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Before using potentially destructive tools** — `rm -rf`, `git reset --hard`, `DROP TABLE` How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Think Tool
Overview
Before making complex or irreversible decisions, stop and think. The Think Tool is a structured reasoning step that happens before you act — not after. It's the difference between guessing and understanding.
Core principle: If you're not sure, think first. If you're sure, think again.
When to Use
Use Think Tool whenever:
- Multiple approaches exist — "I could do X or Y" → Stop, think, decide
- Irreversible changes — Deleting files, modifying database, pushing to main branch
- Complex multi-step operations — More than 3 tool calls in sequence
- Error recovery — Something failed and you're about to try a fix
- Before using potentially destructive tools —
rm -rf,git reset --hard,DROP TABLE - You catch yourself rushing — "Just try this and see" is a red flag
- Ambiguous requirements — Not sure what the user actually wants
Do NOT use for: Simple, obvious operations (single file edit, reading a file, running tests)
How to Think
When you call Think Tool, work through these steps in order:
Step 1: State the Situation
In one sentence, what's happening?
"I need to refactor the ChantingHall feature from 4 files to 2 files."
Step 2: List the Options
What are the possible approaches?
Option A: Merge Manager + UI into one file, keep Types separate Option B: Merge everything into one file Option C: Keep current 4-file structure, just add new features
Step 3: Evaluate Each Option
For each option, answer:
- Pros — What's good about this?
- Cons — What's the risk?
- Effort — How much work?
- Alignment — Does it match the project's existing patterns?
Step 4: Make a Decision
State clearly what you're going to do and why. Then proceed.
"I'll go with Option A because it reduces complexity while keeping type definitions clean and reusable."
Output Format
When using Think Tool, output your reasoning in this format:
🧠 Think Tool
─────────────
Situation: [one sentence]
Options:
1. [Option A] — [brief description]
→ Pros: [...]
→ Cons: [...]
→ Effort: [small/medium/large]
2. [Option B] — [brief description]
→ Pros: [...]
→ Cons: [...]
→ Effort: [small/medium/large]
Decision: [Option X]
Reason: [why this one wins]
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.
- 7d ago First seen · 198 lines · 54 tokens per session scan C b0fbba1de62a
think-tool is a skill published in the GitHub repository ChrisLamDev/hermes-core-skills (9 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,557 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
unicli-repair
Evidence-driven repair workflow for a broken Uni-CLI adapter. Trigger on a failed unicli envelope, a quarantined adapter, or an explicit adapter-repair request. Classifies non-source failures, edits only the reported adapter path, and uses the original command as a bounded oracle.
autonomous-run
Prepare, start, inspect, resume, or stop a finite local overnight coding run after a human has accepted a Wayfinder terminal spec; coordinates a declared Claude/Codex maker and independent checker without pushing, merging, or writing to external systems.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.