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/xiaolai/cc-suite/claude-code-conventionsnpx skills add xiaolai/cc-suite --skill claude-code-conventionsgit clone --depth 1 https://github.com/xiaolai/cc-suiteWrote 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/xiaolai/cc-suite/claude-code-conventions)<a href="https://agentmods.dev/skills/xiaolai/cc-suite/claude-code-conventions"><img src="https://agentmods.dev/badge/skills/xiaolai/cc-suite/claude-code-conventions.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.00051 | $0.02907 |
| Opus 5 | $0.00026 | $0.01453 |
| Sonnet 5 | $0.00010 | $0.00581 |
| Haiku 4.5 | $0.00005 | $0.00291 |
Grade A, and why
claude-code-conventions scanned grade A with 1 finding 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `~/.claude/settings.json` — global user settings Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Plugin Conventions Reference
Purpose: This skill is the single source of truth for Claude Code artifact conventions. Audit commands inject this content into Codex's
developer-instructionsso Codex can accurately validate Claude Code artifacts despite having no native knowledge of the platform.Freshness: Last updated 2026-03-25 from context7 (
/websites/code_claude_en_plugins-reference,/websites/code_claude_en_plugins). Run/cc-suite:refresh-knowledgeto refresh.
When to Use
Load this skill when:
- Auditing Claude Code plugin artifacts (commands, agents, skills, hooks, plugin.json)
- Validating frontmatter fields against the official schema
- Checking hook event names, types, and output formats
- Authoring new plugin artifacts and need the canonical field reference
- Running
/cc-suite:audit-plugin,/cc-suite:audit-command,/cc-suite:audit-agent, or/cc-suite:audit-skill
plugin.json Schema
Only name is strictly required. Version and description are strongly recommended but optional.
Required:
name(string): plugin identifier, kebab-case. Used for namespacing (e.g.,plugin-dev:agent-creator)
Recommended:
version(string): semverX.Y.Z. If also set in marketplace entry, plugin.json takes precedencedescription(string): brief purpose
Optional metadata:
author(object):{ "name": "string", "email": "string", "url": "string" }homepage(string): URL to plugin docsrepository(string): URL to source codelicense(string): SPDX identifier (e.g.,"MIT","Apache-2.0")keywords(string[]): discovery tags
Component path fields (string, string[], or inline object):
commands— path(s) to command files. Default:./commands/(auto-discovered)agents— path(s) to agent files. Default:./agents/(auto-discovered)skills— path(s) to skill directories. Default:./skills/(auto-discovered)hooks— path to hooks config OR inline hooks object. Default:./hooks/hooks.jsonmcpServers— path to MCP config OR inline object. Default:./.mcp.jsonlspServers— path to LSP config. Default:./.lsp.jsonoutputStyles— path to output style definitions
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 · 316 lines · 51 tokens per session scan A be15b35d55fb
claude-code-conventions is a skill published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 2d ago), licensed ISC. It adds 51 tokens to every session and 2,907 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). 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…