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 aegntic/cldcde --skill ae-ltd-claude-template-switchboardgit clone --depth 1 https://github.com/aegntic/cldcdeWrote 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/aegntic/cldcde/ae-ltd-claude-template-switchboard)<a href="https://agentmods.dev/skills/aegntic/cldcde/ae-ltd-claude-template-switchboard"><img src="https://agentmods.dev/badge/skills/aegntic/cldcde/ae-ltd-claude-template-switchboard/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/aegntic/cldcde/ae-ltd-claude-template-switchboard"><img src="https://agentmods.dev/badge/skills/aegntic/cldcde/ae-ltd-claude-template-switchboard.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.00043 | $0.00394 |
| Opus 5.5 | $0.00017 | $0.00158 |
| Sonnet 5.5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
ae-ltd-claude-template-switchboard 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 today.
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
AE.LTD Claude Template Switchboard
What This Skill Does
Routes and customizes CLAUDE.md templates based on repo profile, architecture, and team constraints. Niche gem source: CLAUDE.md templates in awesome-claude-code-toolkit/templates/claude-md.
- Classify repo profile (team size, architecture, compliance)
- Select appropriate template baseline
- Inject repo-specific truths
- Remove template noise and validate executability
Quick Start
User: "Help me set up CLAUDE.md for this monorepo"
→ Classify profile → Pick template → Inject truths → Validate
Template Routing
minimal: scripts or tiny repos.standard: most single-app repos.monorepo: multi-package workspace (Turborepo/Nx/pnpm workspaces).enterprise: compliance-heavy org environments.python-project: Python-first app stack.fullstack-app: frontend + API product stack.
Workflow
-
Classify repo profile. Team size, architecture, compliance needs, and tooling maturity.
-
Pick closest template baseline. Start from one template only, then layer project specifics.
-
Inject repo truths. Commands, folder map, test strategy, release flow, and non-negotiable rules.
-
Remove template noise. Delete irrelevant sections rather than keeping generic placeholders.
-
Validate executability. Every command and path in CLAUDE.md must exist or be updated.
Guardrails
- Avoid overlong CLAUDE.md files with duplicate guidance.
- Keep conventions enforceable, not aspirational.
- Prefer concrete examples over policy prose.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 55 lines · 43 tokens per session scan A 8d0249158a03
ae-ltd-claude-template-switchboard is a skill published in the GitHub repository aegntic/cldcde (11 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 394 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-11-05.
Other skills, from other repositories
hono-core
Hono ultrafast web framework fundamentals - routing, context, handlers, and response patterns for multi-runtime deployment.
tauri-django-react
Agents should invoke this skill for Tauri + Django + React desktop apps, especially backend lifecycle, CORS/auth, frontend integration, mandatory light/dark theming, German/English i18n, build packaging, dual desktop/web deployment, Rust commands, and platform-specific gotchas.
rewrite-in-rust
Assess, plan, execute, and verify migrations of existing software to Rust. Use for requests to rewrite, port, migrate, or oxidize a codebase, library, module, application, or subsystem in Rust, including RIIR requests. Adapts to the source language and repository; supports incremental replacement, a separate complete…
project-readme
Use when creating, updating, reviewing, restructuring, or harmonizing a repository's project README from verified local evidence for user-oriented or developer/library-oriented readers, with separately approved TECHNICAL.md and DEVELOPMENT.md companions when needed.
requirements-engineering
Elicits, documents, checks, and agrees on requirements with users and stakeholders. Separates problem, requirement, and solution, and keeps evidence, agreement, and approval apart. Use this skill for requirements, specifications, user stories, feature requests, stakeholder interviews, workshops, surveys, requirements…
repo-explorer
Agents should invoke this skill before modifying unfamiliar codebases, answering where/how something is implemented, tracing dependencies, mapping repo structure, or planning changes. Explores a repository and returns a strict JSON handoff with key files, symbols, risks, and evidence.