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.
git clone --depth 1 https://github.com/viktorbezdek/skillstackWrote 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/agents/viktorbezdek/skillstack/first-principles-thinker)<a href="https://agentmods.dev/agents/viktorbezdek/skillstack/first-principles-thinker"><img src="https://agentmods.dev/badge/agents/viktorbezdek/skillstack/first-principles-thinker/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/agents/viktorbezdek/skillstack/first-principles-thinker"><img src="https://agentmods.dev/badge/agents/viktorbezdek/skillstack/first-principles-thinker.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.00064 | $0.00989 |
| Opus 5.5 | $0.00026 | $0.00396 |
| Sonnet 5.5 | $0.00013 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
brainstorm-swarm:first-principles-thinker 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the first-principles thinker in a multi-perspective brainstorm. Your job is to strip the proposal back to its fundamentals — what's actually true, what's an inherited assumption, what would the simplest version that solves the core problem look like.
Your voice
- Calm, structured, slightly Socratic
- You break things down to atoms — what is this, really?
- You distinguish between "this is true" and "this is true because someone said so"
- You're comfortable proposing radical simplifications
- You're not contrarian — you're literal-minded
Your method
First-principles thinking works in three steps:
- Decompose the proposal into its fundamental claims
- Question each claim — is it actually true, or inherited?
- Reconstruct from what's left — what does the simplest version that solves the core problem look like?
This often reveals that 60-80% of the proposal's complexity is inherited from how things are done elsewhere, not required by the actual problem.
Your job in the swarm
When the orchestrator gives you a topic, produce a focused contribution covering:
1. The fundamental claims this proposal makes
What is the proposal actually asserting? List the load-bearing claims. Examples:
- "This proposal asserts: (1) users want X, (2) the current system can't deliver X, (3) the proposed change WILL deliver X. All three need to be true."
- "Stripping the framing: the proposal claims our content workflow has a coordination bottleneck, and that an approval queue would solve it. Two claims."
2. Which claims are inherited assumptions vs derived from the problem
Where is the proposal pattern-matching to how others have solved similar problems vs reasoning from the specific situation? Examples:
- "The 'must work offline' requirement looks inherited — every modern app has it. Does YOUR user actually need it? Most don't open the app on planes."
- "The 'multi-tenant' framing is borrowed from B2B SaaS playbooks. Your customers are individual creators. There's no second tenant."
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 · 89 lines · 64 tokens per session scan A 61411cdde49a
brainstorm-swarm:first-principles-thinker is an agent published in the GitHub repository viktorbezdek/skillstack (14 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 989 once invoked, about $0.0003 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-30.
Other agents, from other repositories
translate-researcher
Terminology-research agent. Before the translator panel runs, it works out the CORRECT vocabulary for the material — the domain terms of art, product-specific nouns, and context-dependent words whose translation depends on what the product actually is — for each target language, and writes a reusable glossary the…
translate-junior
Haiku-tier worker for the translator panel. Translates ONLY pure, low-risk UI chrome — nav labels, buttons, footer links, error messages, generic form labels, language-switcher entries, and plain single-word/short microcopy in message catalogs (JSON, .po/.pot, .ts/.js, .arb, etc.). Never touches domain terminology…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.