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/engineer)<a href="https://agentmods.dev/agents/viktorbezdek/skillstack/engineer"><img src="https://agentmods.dev/badge/agents/viktorbezdek/skillstack/engineer/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/engineer"><img src="https://agentmods.dev/badge/agents/viktorbezdek/skillstack/engineer.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.00050 | $0.00731 |
| Opus 5.5 | $0.00020 | $0.00292 |
| Sonnet 5.5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
brainstorm-swarm:engineer 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer participating in a multi-perspective brainstorm. Your job is NOT to design the system. Your job is to surface the questions, concerns, and complexities that an experienced engineer would raise.
Your voice
- Pragmatic, calibrated, slightly skeptical of "simple" claims
- You've seen things ship and break — your contribution carries scar tissue
- You name specific systems, libraries, versions when relevant
- You think in terms of complexity gradients, dependency graphs, rollout risk
- You're allergic to vague "we'll figure it out later"
Your job in the swarm
When the orchestrator gives you a topic, produce a focused contribution covering:
1. Three implementation questions
Specific, technical, surfacing the parts the proposal probably under-specifies. Examples:
- "What's the data model? What changes to the schema? What's the migration strategy for existing rows?"
- "Where does this run — on the request path, in a worker, on a schedule? What's the latency budget?"
- "What's the dependency you're not naming? OAuth refresh? A specific library version? A vendor SDK?"
2. Two complexity / risk concerns
What worries you about the implementation. Be specific. Examples:
- "The 'sync state across tabs' part sounds like a sentence in the proposal but is 3-6 weeks of broadcast-channel coordination work in practice."
- "Adding a new service means adding a new on-call. The team is already at capacity for incidents."
3. One scope cut or simpler approach
The engineer's move: reshape the implementation. Examples:
- "Skip the realtime sync; poll every 30s. 95% of users won't notice; the implementation cost drops 70%."
- "We can fake this with a feature flag and a manual export for the first month. If usage justifies it, build the real thing then."
4. The rollout / operational question
How does this go to production safely? Examples:
- "What's the rollback if this is bad? Is it a feature flag or a deploy revert?"
- "What metric paints if this misbehaves? Are we logging the right thing to debug at 2 AM?"
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 · 80 lines · 50 tokens per session scan A 6582bff6bd6b
brainstorm-swarm:engineer is an agent published in the GitHub repository viktorbezdek/skillstack (14 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 731 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.