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/constitution-buildernpx skills add TentacleOpera/switchboard --skill constitution-buildergit 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.00427 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
constitution-builder 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: Constitution Builder
Overview
Interview-style skill to build or improve a lean, high-level CONSTITUTION.md focusing on the soul of the project (mission, target users, guiding principles, stack constraints, and non-goals) rather than detailed coding standards or formatting guidelines.
Usage
When invoked to build or improve a constitution, lead the user through a structured interview process or gather context from the existing codebase to assemble and refine the constitution file.
Process
1. Context Collection & Interview
Prompt the user with target questions or propose answers based on repository analysis:
- Mission: What is the name of this project, and in one sentence, what is its primary reason for existing?
- Target Users: Who are the primary users, and what is their main pain point?
- Guiding Principles: What are the 3–5 non-negotiable values that should govern every technical and product decision? Give each a short name and one concrete sentence explaining what it means in practice.
- Technical Constraints: What are the hard technical boundaries? List required languages, core frameworks, data stores, and key third-party services.
- Non-Goals: What are specific things this project will NOT do in its current scope? (Prevents scope creep.)
2. Document Construction
Write the draft or updated sections strictly adhering to this template:
# [Project Name] Constitution
> **Mission:** [one sentence]
## Guiding Principles
- **[Name]:** [concrete explanation]
## Target Users
[Who they are and their main pain point]
## Technical Constraints & Stack
- Core Language & Frameworks: ...
- Data Layer: ...
- Key External Services: ...
## Non-Goals
- [Explicit exclusion 1]
- [Explicit exclusion 2]
Keep the document short (under 150 lines total). Do not include coding conventions, formatting standards, or test suites, as these belong in CLAUDE.md or .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.
- 2d ago First seen · 44 lines · 0 tokens per session scan A b84a5a68148d
constitution-builder is a skill published in the GitHub repository TentacleOpera/switchboard (213 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 427 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.