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 celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-coding-standardsgit clone --depth 1 https://github.com/celticht32/Couchbase-Skills-for-Claude.aiWrote 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/celticht32/couchbase-skills-for-claude.ai/couchbase-coding-standards)<a href="https://agentmods.dev/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-coding-standards"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-coding-standards/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/celticht32/couchbase-skills-for-claude.ai/couchbase-coding-standards"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-coding-standards.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.00209 | $0.01398 |
| Opus 5 | $0.00105 | $0.00699 |
| Sonnet 5 | $0.00042 | $0.00280 |
| Haiku 4.5 | $0.00021 | $0.00140 |
Grade A, and why
couchbase-coding-standards 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Couchbase coding standards & style guide
A skill for writing and reviewing clean, correct, maintainable application code against Couchbase. It combines general software-engineering discipline with the Couchbase-specific conventions that keep application code idiomatic, safe, and resilient.
Distinct from:
couchbase-app-integration— SDK mechanics (connection pooling, durability levels, scan consistency, retry primitives). This skill assumes those mechanics and covers how to write the code around them well.couchbase-data-modeling— what shape the documents take. This skill covers how the code that reads and writes them is structured and named.couchbase-sqlpp-tuning— query performance. This skill covers query safety in code (parameterization, injection, result handling).
If the conversation is "how should this Couchbase code be written / named / structured / reviewed," this is the right skill.
When this skill applies
- "What are the coding standards / style guide for Couchbase apps?"
- "Review this Couchbase code."
- "How should I name my document keys / SDK objects / functions?"
- "Is this idiomatic use of the SDK?"
- "How do I handle Couchbase errors properly in code?"
- "How do I write testable code against Couchbase?"
- "How do I avoid SQL++ injection?"
- "Set up linting / formatting / a review checklist for a Couchbase project."
Pick the right reference
| Question | Read |
|---|---|
| "General clean-code standards — naming, functions, comments, tests, version control, reviews, secrets" | references/general-coding-standards.md |
| "Idiomatic SDK use — connection lifecycle, KV vs query, batching, async, per-language idioms" | references/couchbase-sdk-idioms.md |
| "Document key + field naming conventions, type discriminators, metadata fields" | references/key-and-document-conventions.md |
| "Couchbase exceptions, retry/backoff, idempotency, durability in code, transactions hygiene" | references/error-handling-and-resilience.md |
| "Writing SQL++ in application code safely — parameterization, injection, scan consistency, pagination" | references/sqlpp-in-code.md |
What ships with it
5 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.
- 11d ago First seen · 71 lines · 209 tokens per session scan A baf3d0efa8b6
couchbase-coding-standards is a skill published in the GitHub repository celticht32/Couchbase-Skills-for-Claude.ai (4 stars, last pushed 2mo ago), licensed MIT. It adds 209 tokens to every session and 1,398 once invoked, about $0.0010 per session on Opus 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-08-31.
Other skills, from other repositories
gemini
Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
refactor
Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…