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 skills/tentacleopera/switchboard/complexity-scoringnpx skills add TentacleOpera/switchboard --skill complexity-scoringgit clone --depth 1 https://github.com/TentacleOpera/switchboardWhat 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.00000 | $0.00385 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
complexity-scoring 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 2d 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.
What it actually says
Skill: Complexity Scoring
Overview
Assess and assign numeric complexity scores (1-10) to plans and tasks.
Usage
When asked to estimate complexity, create a plan, or review complexity:
- Reference this skill
- Apply the scoring criteria below
- Output
**Complexity:** [N]where N is 1-10
Scoring Criteria
1-2: Very Low
- Trivial config or copy changes
- Single-line fixes
- No logic changes
3-4: Low
- Routine single-file changes
- Reuses existing patterns
- Low risk, no architectural changes
- Typically <20 lines of code
5-6: Medium
- Multi-file changes (2-3 files)
- Moderate logic additions
- Extends existing patterns
- Some cross-component coordination
7-8: High
- New architectural patterns
- Complex state management
- Security-sensitive changes
- Breaking changes to core data structures
9-10: Very High
- Architectural rewrites
- New framework integrations
- Multi-system coordination with tight coupling
- Fundamental schema or API changes
Examples
| Task | Score | Rationale |
|---|---|---|
| Fix a CSS color | 3 | Single file, routine change |
| Add a new button using existing handler | 4 | Single file, reuses pattern |
| Add validation across frontend + backend | 6 | Multi-file, moderate logic |
| Implement new auth middleware | 7 | New pattern, security-critical |
| Migrate to new database layer | 9 | Architectural rewrite |
Output Format
Always use this exact format in plan metadata:
## Metadata
**Tags:** [comma-separated from allowed list]
**Complexity:** [integer 1-10]
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.
- 2d ago First seen · 63 lines · 0 tokens per session scan A 35ff1c97c245
complexity-scoring is a skill published in the GitHub repository TentacleOpera/switchboard (213 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 385 tokens. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…