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 neurofoo/agent-skills --skill sixhatsgit clone --depth 1 https://github.com/neurofoo/agent-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/neurofoo/agent-skills/sixhats)<a href="https://agentmods.dev/skills/neurofoo/agent-skills/sixhats"><img src="https://agentmods.dev/badge/skills/neurofoo/agent-skills/sixhats.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.00039 | $0.00642 |
| Opus 5 | $0.00019 | $0.00321 |
| Sonnet 5 | $0.00008 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
sixhats 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Six Thinking Hats Analysis
Explore a topic from all six perspectives—facts, feelings, caution, benefits, creativity, and process.
Instructions
Work through each hat sequentially, giving full attention to one perspective before moving to the next. This is parallel thinking, not debate.
Output Format
Topic: [What we're exploring]
White Hat: Facts and Information
What do we know? What data do we have?
Known Facts
- [Fact 1]
- [Fact 2]
Information Gaps
- What don't we know? [Gap]
- How could we find out? [Method]
Red Hat: Feelings and Intuition
How do we feel about this? What does gut instinct say?
Emotional Reactions
- [Feeling 1]
- [Feeling 2]
Intuitions
- My gut says [intuition]
No justification needed—this hat is about feelings, not reasons.
Black Hat: Caution and Critical Thinking
What could go wrong? What are the risks and problems?
Risks
| Risk | Likelihood | Severity |
|---|---|---|
| [risk] | High/Med/Low | High/Med/Low |
Why It Might Fail
- [Reason 1]
- [Reason 2]
Yellow Hat: Benefits and Optimism
What's good about this? What value does it offer?
Benefits
| Benefit | Who Benefits | Magnitude |
|---|---|---|
| [benefit] | [stakeholder] | High/Med/Low |
Best Case Scenario If everything goes well: [description]
Green Hat: Creativity and Alternatives
What else is possible? What new ideas emerge?
Alternative Approaches
- [Alternative 1]
- [Alternative 2]
Wild Ideas (don't filter)
- [Crazy idea 1]
- [Crazy idea 2]
Blue Hat: Process and Meta-Thinking
What have we learned? What should we do next?
Summary of Perspectives
| Hat | Key Insight |
|---|---|
| White | [main data point] |
| Red | [main feeling] |
| Black | [main concern] |
| Yellow | [main benefit] |
| Green | [best alternative] |
Recommended Next Steps
- [Action 1]
- [Action 2]
Decision/Direction Based on all six perspectives:
[Recommendation or decision]
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 · 118 lines · 39 tokens per session scan A 49139dff049c
sixhats is a skill published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 642 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-30.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…