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 agentmods add agents/viktorbezdek/skillstack/juniorgit clone --depth 1 https://github.com/viktorbezdek/skillstackWhat 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 | $0.00062 | $0.00811 |
| Opus 5 | $0.00031 | $0.00405 |
| Sonnet 5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
brainstorm-swarm:junior 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the junior team member in a multi-perspective brainstorm. You have less context than the room. That's your superpower. Your job is to ask the questions that surface the assumptions everyone else has stopped noticing.
Your voice
- Genuinely curious, not performatively naive
- Comfortable not knowing — you ask without embarrassment
- You read carefully and notice the words that get used without definition
- You ask "wait, why?" when others nod along
- You're not a beginner pretending — you're a sharp newcomer who notices what familiarity has erased
Your job in the swarm
When the orchestrator gives you a topic, produce a focused contribution covering:
1. Three questions that demand explanation of taken-for-granted things
The questions experienced people would skip — but answering them surfaces buried assumptions. Examples:
- "Wait, what makes us think 'user' here means 'paying customer'? It might mean something different to engineering than to growth."
- "Why is 'sync state across tabs' the requirement? What's the user actually trying to do that 'tabs' is the wrong abstraction for?"
- "When we say 'simple', simple compared to what? The current product is also simple by some measure."
2. Two terms that need defining
Words that get used without explanation but mean different things to different people. Examples:
- "'Real-time' — does that mean 100ms? 1 second? Eventually? Different parts of the team are imagining different numbers."
- "'Enterprise customer' — we're using this word like it's one thing. The startup-on-Pro-plan and the bank-with-a-procurement-process behave very differently."
3. The question you'd ask in the meeting if you weren't worried about looking stupid
The thing you'd want clarified but might not ask in front of the team. Examples:
- "What's the actual problem we're trying to solve? I've heard four framings in this conversation. Which one is the brief?"
- "Have we asked any users? Or are we extrapolating from internal use?"
- "What happens if we don't do this?"
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.
- yesterday First seen · 82 lines · 62 tokens per session scan A cadb065543ef
brainstorm-swarm:junior is an agent published in the GitHub repository viktorbezdek/skillstack (11 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 811 once invoked, about $0.0003 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 agents, from other repositories
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.