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 askarzh/epistemator --skill sixhatsgit clone --depth 1 https://github.com/askarzh/epistematorWrote 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/askarzh/epistemator/sixhats)<a href="https://agentmods.dev/skills/askarzh/epistemator/sixhats"><img src="https://agentmods.dev/badge/skills/askarzh/epistemator/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.00080 | $0.01883 |
| Opus 5 | $0.00040 | $0.00941 |
| Sonnet 5 | $0.00016 | $0.00377 |
| Haiku 4.5 | $0.00008 | $0.00188 |
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 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.
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.
Six Thinking Hats (De Bono)
Overview
Apply Edward de Bono's Six Thinking Hats method — a structured parallel thinking framework that separates thinking into six distinct modes, each represented by a colored hat. By wearing one hat at a time, thinkers avoid the confusion of mixing facts with emotions, criticism with creativity, and analysis with action.
This is a thinking organization tool, not a truth-finding or analytical framework. It does not determine what is true (use Scholastic for that) or decompose complexity (use Cartesian for that). Its power is in ensuring that all relevant cognitive modes — factual, emotional, critical, optimistic, creative, procedural — are exercised deliberately rather than haphazardly. The output is a structured map of perspectives, not a resolved conclusion.
The Six Hats method excels at decisions, evaluations, planning, and any input where multiple perspectives need to be explored without the chaos of unstructured debate.
The Six Hats
| Hat | Focus | Key Question |
|---|---|---|
| ⚪ White — Facts | Objective data, information, what is known and what is missing | "What do we know? What do we need to find out?" |
| 🔴 Red — Feelings | Intuitions, emotions, gut reactions — no justification required | "What is my gut feeling about this?" |
| ⚫ Black — Caution | Risks, dangers, problems, weaknesses, why it might fail | "What could go wrong?" |
| 🟡 Yellow — Optimism | Benefits, value, feasibility, why it might work | "What are the benefits? Why is this worth doing?" |
| 🟢 Green — Creativity | Alternatives, new ideas, possibilities, provocations, modifications | "What are the alternatives? What new ideas emerge?" |
| 🔵 Blue — Process | Meta-thinking, organization, summary, conclusions, next steps | "What have we learned? What should we do next?" |
Core Methodology
- 🔵 Blue Hat Opening — Define the focus. What is the topic, question, or decision? What outcome is needed? Set the sequence of hats to use. The default order below (White → Red → Black → Yellow → Green) works for most situations, but adapt it: start with Red if emotions are running high and need acknowledgment first; start with Black if the proposal seems risky and caution is the priority; skip Green if no alternatives are needed.
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 · 134 lines · 80 tokens per session scan A 9504ca0ae36e
sixhats is a skill published in the GitHub repository askarzh/epistemator (3 stars, last pushed 6mo ago), licensed MIT. It adds 80 tokens to every session and 1,883 once invoked, about $0.0004 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
add-cloud-flow
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.