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 parisgroup-ai/imersao-ia-setup --skill team-plangit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/team-plan)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/team-plan"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/team-plan/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/parisgroup-ai/imersao-ia-setup/team-plan"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/team-plan.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.00062 | $0.03186 |
| Opus 5.5 | $0.00025 | $0.01274 |
| Sonnet 5.5 | $0.00012 | $0.00637 |
| Haiku 4.5 | $0.00006 | $0.00319 |
Grade A, and why
team-plan 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 21d 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Plan
Scatter-gather planning team. Spawns research agents in parallel, gathers codebase context and requirements analysis, consolidates into an implementation plan compatible with /team-execute and /plan-to-tasks.
Usage
/team-plan "Add badge system for students" # Default scope (medium)
/team-plan "Add badge system" --scope large # Full research (3 agents)
/team-plan "Fix login redirect" --scope small # Quick plan (1 agent)
/team-plan "Add badge system" --output my-badges # Custom output filename
Parse Arguments
Extract from: {{ARGUMENTS}}
FEATURE = quoted string or remaining text after flags
SCOPE = small | medium | large (default: medium)
OUTPUT = --output value or auto-generated from FEATURE
If no arguments or FEATURE is empty, show help and stop:
/team-plan - Create implementation plans with parallel research agents
Usage:
/team-plan "Add user badges" Medium scope (2 agents)
/team-plan "Add badges" --scope large Full research (3 agents)
/team-plan "Fix redirect" --scope small Quick plan (1 agent)
/team-plan "Add badges" --output badge-plan Custom filename
Pipeline: RESEARCH (parallel) → CONSOLIDATE → OUTPUT
Agents: researcher + analyst [+ ux-mapper]
Output: .claude/plans/{date}-{slug}.md
Next steps after plan:
/team-execute <plan> Execute with agent team
/plan-to-tasks import <plan> Import to TaskNotes
Phase 1: PREPARE
Generate Plan Metadata
SLUG = slugify(FEATURE) # e.g., "add-badge-system"
DATE = YYYY-MM-DD # today
PLAN_PATH = .claude/plans/{DATE}-{OUTPUT or SLUG}.md
Verify .claude/plans/ directory exists (create if not).
Phase 2: SCATTER (Spawn Research Agents)
Agent Selection
If SCOPE = small:
agents = [researcher] # 1 agent
If SCOPE = medium:
agents = [researcher, analyst] # 2 agents
If SCOPE = large:
agents = [researcher, analyst, ux-mapper] # 3 agents
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.
- 21d ago First seen · 457 lines · 62 tokens per session scan A 821a42d17f8c
team-plan is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 20d ago), licensed MIT. It adds 62 tokens to every session and 3,186 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-10-06.
Other skills, from other repositories
technical-documentation
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or…
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
crossing-the-chasm
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…