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/tuningnpx skills add TentacleOpera/switchboard --skill tuninggit clone --depth 1 https://github.com/TentacleOpera/switchboardWrote 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/tentacleopera/switchboard/tuning)<a href="https://agentmods.dev/skills/tentacleopera/switchboard/tuning"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/tuning.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00531 |
| Opus 5 | $0.00000 | $0.00266 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
tuning 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 4d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tuning Skill
Purpose
Extract recurring problem patterns from adversarial review sections in completed/reviewed plans, store them as individual insight documents, and propose governance file updates.
Modes
Extract Mode
Receive a list of plan file paths and scan each for adversarial review sections ("Stage 1 — Grumpy Adversarial Findings" and "Stage 2 — Balanced Synthesis"). Cluster recurring problem patterns across plans and create individual insight .md files in {workspaceRoot}/.switchboard/insights/.
Clustering criteria:
- Same problem category (e.g., missing error handling, race conditions, prompt-design flaws, unvalidated assumptions)
- Same severity level (recurring vs critical vs minor)
- Same governance target (CONSTITUTION.md vs AGENTS.md vs CLAUDE.md)
Deduplication: Before creating a new insight, check existing insights in .switchboard/insights/. If an existing insight covers the same pattern (same category AND similar description), append new evidence to it instead of creating a duplicate. When appending, update the Source Plans list and add new evidence entries.
Governance Mode
Read all insight files in {workspaceRoot}/.switchboard/insights/ with status open. Review the insights and propose specific edits to governance files (CONSTITUTION.md, AGENTS.md, CLAUDE.md) to address the recurring patterns. Present proposed changes as diffs.
Insight File Template
# [Insight Title]
## Metadata
**Created:** [date]
**Source Plans:** [list of plan filenames that contributed this pattern]
**Severity:** [recurring | critical | minor]
**Status:** [open | applied | dismissed]
## Problem Pattern
[Description of the recurring issue observed across plans]
## Evidence
- **[plan-filename.md]**: [specific quote or paraphrase from the adversarial section]
- **[plan-filename.md]**: [specific quote or paraphrase]
## Recommendation
[Suggested rule or invariant to add to governance files]
## Suggested Governance Target
[CONSTITUTION.md | AGENTS.md | CLAUDE.md | .cursor/rules/]
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.
- 4d ago First seen · 57 lines · 0 tokens per session scan A f7ff969befcc
tuning is a skill published in the GitHub repository TentacleOpera/switchboard (213 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 531 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…