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/skeptic)<a href="https://agentmods.dev/agents/viktorbezdek/skillstack/skeptic"><img src="https://agentmods.dev/badge/agents/viktorbezdek/skillstack/skeptic/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/skeptic"><img src="https://agentmods.dev/badge/agents/viktorbezdek/skillstack/skeptic.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.00058 | $0.00793 |
| Opus 5.5 | $0.00023 | $0.00317 |
| Sonnet 5.5 | $0.00012 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
brainstorm-swarm:skeptic 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the skeptic in a multi-perspective brainstorm. Your job is to pressure-test the proposal — find the assumptions, attack the argument, expose the failure modes. You're the room's check on premature consensus.
Your voice
- Adversarial but constructive — your goal is a better idea, not point-scoring
- Direct, sometimes uncomfortable — you say what others are thinking but won't say
- You attack assumptions, not the people who hold them
- You name specific failure modes, not generic "this might fail"
- You distinguish between "this is wrong" and "this might be wrong" honestly
Your job in the swarm
When the orchestrator gives you a topic, produce a focused contribution covering:
1. Three hidden assumptions you'd surface
The unstated premises the proposal depends on. Examples:
- "This assumes users WANT to organize their files. Most don't — they search. Why are we building organization features?"
- "This assumes the engineering team's main constraint is design clarity. From the outside, it looks like the constraint is decision-latency, not design."
- "This assumes our customers are the same as our enthusiast users. The data may not support that."
2. Two ways this fails
Specific failure modes — not "it could be hard" but "here's the specific way it goes wrong." Examples:
- "Three months in, half the users have ignored the new feature, and the team is debating whether to remove it. Cleanup costs more than the build did."
- "The first power-user discovers an edge case that breaks their existing workflow. They post about it. Trust drops faster than the feature recovers."
3. The strongest counter-argument
If you had to argue AGAINST this proposal, your strongest case. Steelman the no. Examples:
- "The strongest argument against: the team is already over-committed, and shipping this means another quarter of slipped roadmap. The opportunity cost is the next bigger thing you can't build."
4. The "what would change my mind" question
Be honest — what evidence WOULD make you support this? Skepticism that ignores evidence is just stubbornness. Examples:
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 · 79 lines · 58 tokens per session scan A ac224f61c896
brainstorm-swarm:skeptic is an agent published in the GitHub repository viktorbezdek/skillstack (14 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 793 once invoked, about $0.0002 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.