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 NikiforovAll/claude-code-rules --skill team-stackgit clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWrote 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/nikiforovall/claude-code-rules/team-stack)<a href="https://agentmods.dev/skills/nikiforovall/claude-code-rules/team-stack"><img src="https://agentmods.dev/badge/skills/nikiforovall/claude-code-rules/team-stack/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/skills/nikiforovall/claude-code-rules/team-stack"><img src="https://agentmods.dev/badge/skills/nikiforovall/claude-code-rules/team-stack.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.00060 | $0.01304 |
| Opus 5.5 | $0.00024 | $0.00522 |
| Sonnet 5.5 | $0.00012 | $0.00261 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
team-stack 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 25d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Stack: Analyze, Propose, and Create Agent Teams
You help the user set up the right agent team for their task. You do NOT ask the user about preferences or scope — you infer everything from the task description and codebase context.
Phase 1: Analyze the Task
When the user describes a task (or you receive one), analyze it to determine:
- Task type: feature, bugfix, refactor, review, migration, investigation, etc.
- Scope: how many files/modules/layers are involved — use
git status,git diff, file reads, and grep to understand the affected surface area - Parallelization potential: which parts of the work are independent and can run concurrently vs. which have dependencies
- Risk level: does it touch critical paths, shared state, or public APIs
- Knowledge gaps: areas of the codebase or problem domain that are not yet well understood
Use Existing Context
If there is an active plan, ADR, or task list, use it as the primary input instead of re-analyzing from scratch.
Explore the Codebase
Explore areas relevant to the task when needed — especially when modules are unfamiliar, conventions need verification, or dependencies are unclear. Explore independent areas concurrently.
Do this analysis silently. Do NOT present it to the user as a separate step.
Phase 2: Propose Team Stack
Based on your analysis, propose a team. Present it to the user as a clear table:
## Proposed Team: <team-name>
| Role | Name | Responsibility | Isolation |
|------|------|---------------|-----------|
| ... | ... | ... | worktree / shared |
**Why this composition:** <1-2 sentences explaining the rationale>
Team Composition Guidelines
Pick the minimum viable team. Do not over-staff.
Solo agent (no team needed):
- Simple, single-file changes
- Quick fixes with obvious solutions
- Suggest using a subagent instead and exit
2 agents:
- Task has two clearly independent workstreams (e.g., frontend + backend, implementation + tests)
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.
- 25d ago First seen · 137 lines · 60 tokens per session scan A d5a62d544ef5
team-stack is a skill published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 14d ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,304 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-09-21.
Other skills, from other repositories
review-pr
Review a Pull Request in one of two postures: an expository "tour guide" that walks through changes in logical order, or an adversarial audit that assumes the change is wrong until proven safe and hunts for the failure mode. Triggers: "review PR #123", "adversarial review", "walk me through this PR", "PR tour guide"…
researcher
Use when asked to create research documents, generate PDFs, make one-pagers, or create cheatsheets. Triggers: "research document", "generate PDF", "one-pager", "cheatsheet", "distinctive design". Provides HTML/Markdown/PDF with Terminal, Editorial, Corporate, Industrial, Fresh aesthetic presets.
svg-mastery
Expert knowledge for working with SVG (Scalable Vector Graphics) — optimization, embedding, animation, accessibility, responsive scaling, React integration, filters, and programmatic creation. Use when the user asks to "optimize SVG", "clean up SVG", "reduce SVG file size", "embed SVG in HTML", "inline SVG vs img…
demo-graphics
Dresses the Final Cut Pro finish of a demo video with Motion templates — MotionVFX DesignStudio elements downloaded through mExtension first, Final Cut Pro's built-in templates otherwise. Inventories what is installed (downloaded or only a placeholder), picks one look and one element per role from the footage — title…
demo-video
Orchestrates building a narrated demo video of a project — reads the codebase, writes a storyboard, prepares deterministic app state, drives the UI with Playwright to record clips (web and Electron, recorded by Playwright or by OBS), generates ElevenLabs voiceover, reconciles measured durations into a timeline, and…
icon-library
Fetch pre-made SVG icons from open-source icon libraries (Lucide, Heroicons, Tabler Icons) for use in websites, presentations, Figma designs, or any project. Use when the user asks to "add an icon", "use a search icon", "find an icon for settings", "get SVG icons", or needs clean SVG icons. NEVER draw icons manually …