agentmods.dev

SQLiteCpp: Skill for Claude Code

.claude/skills/sqlitecpp-workflow/SKILL.md

sqlitecpp-workflow is a skill for Claude Code from SRombauts/SQLiteCpp. It costs 31 tokens per session (1,442 once invoked), scanned A, original, MIT.

A contribution workflow for the SQLiteCpp C++ library, covering code changes, tests, documentation, build files, commits, pull requests, and release notes. SQLiteCpp is a C++ interface for working with SQLite databases.

In plain words
What is it for?
Use it when changing SQLiteCpp: create the required branch, add tests and API documentation, update build files and the changelog, run checks, and commit the work.
Why use it?
It provides a checklist for repository changes so implementation, tests, public documentation, build configuration, and release notes are not forgotten.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions AGENTS.md.

This is SRombauts/SQLiteCpp's own configuration. It tells Claude Code how to work on SQLiteCpp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SQLiteCpp configures →

not rated 2.8krepo +6 changed 22d ago A scan SkillSpector: pass 31 tokens original MIT
View source ↗ SRombauts/SQLiteCpp srombauts.github.io
About the project

SQLiteC++ is a C++ wrapper around SQLite's native C interface, providing classes for working with SQLite databases. It is used by C++ developers who want a lightweight interface with standard library types, exceptions, and resource management. The catalogue entries provide skills for working with the library.

SRombauts/SQLiteCpp · 2,808 stars · on GitHub · srombauts.github.io

Reuse

Borrowing it

Nothing to install: this file belongs to SRombauts/SQLiteCpp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SRombauts/SQLiteCpp/master/.claude/skills/sqlitecpp-workflow/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/SRombauts/SQLiteCpp

Made for: Claude Code.

Wrote 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.

agentmods badge for sqlitecpp-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/srombauts/sqlitecpp/sqlitecpp-workflow/github.svg)](https://agentmods.dev/skills/srombauts/sqlitecpp/sqlitecpp-workflow)
Your own site
<a href="https://agentmods.dev/skills/srombauts/sqlitecpp/sqlitecpp-workflow"><img src="https://agentmods.dev/badge/skills/srombauts/sqlitecpp/sqlitecpp-workflow/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.

agentmods 80×15 button for sqlitecpp-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/srombauts/sqlitecpp/sqlitecpp-workflow"><img src="https://agentmods.dev/badge/skills/srombauts/sqlitecpp/sqlitecpp-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,442 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01442
Opus 5.5 $0.00012 $0.00577
Sonnet 5.5 $0.00006 $0.00288
Haiku 4.5 $0.00003 $0.00144

Measured 22d ago against content hash e1388691f70f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sqlitecpp-workflow 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 22d 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.

.claude/skills/sqlitecpp-workflow/SKILL.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SQLiteCpp Workflow

Required workflow

For an implementation request, complete the local Git workflow before handing the work back:

  1. Load sqlitecpp-git-branching, inspect git status, and create the task branch before editing.
  2. Implement the change and its tests, public API documentation, and any required build-file updates.
  3. Build and run the relevant tests.
  4. Commit the completed work according to the atomic and independent commit rules below.
  5. Report the branch name, commit hashes, and validation results.

If work was accidentally started on master, create the correctly named branch immediately while preserving the working tree, then continue the workflow there. Do not leave completed implementation changes uncommitted unless the user explicitly asks for an uncommitted patch.

Change checklist

  • Public API has Doxygen (@brief, @param, @return, @throw).
  • Tests added under tests/.
  • Build files updated (CMakeLists.txt, meson.build).
  • CHANGELOG.md updated for user-facing changes (in a separate commit after opening the PR).

CHANGELOG conventions

If the user explicitly requests no CHANGELOG change or entry, leave CHANGELOG.md unchanged.

Update CHANGELOG.md in the same PR that makes the change, but in a separate commit created after the PR is opened so the PR number is known. Normally add one line per PR under the current unreleased version heading (Version X.Y.Z - <year> ???). Create that heading if it does not exist yet.

  • Append a new bullet at the end of the current unreleased section by default. Do not reorder existing entries or insert the new entry by category unless there is a clear reason to group related changes.
  • Related PRs may be kept together or combined when that makes the history clearer. For example, keep consecutive updates to the bundled SQLite library together instead of separating them by append order.
  • Normally use one bullet per PR: - <description> (#NNN). Keep all PR numbers at the end when related PRs share an entry: - <description> (#NNN) (#MMM).
  • Write in the imperative mood, present tense: "Add", "Fix", "Update", "Remove". Not "Added", "Fixes", or "Adding".
  • Keep each entry to a single line that names the user-facing effect, not the internal mechanics.
  • A change merged straight to master without a PR still gets a bullet; omit the (#NNN) and note it was committed directly to master.
  • ASCII only, no em dashes. Run the entry through the humanizer skill before committing so the prose stays plain and free of AI tells.

Read the full file on GitHub · 107 lines

Changes

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.

  1. 22d ago Changed · +5 lines e1388691f70f
  2. 1mo ago Changed · +4 lines 11887d8c1ed7
  3. 1mo ago Changed · +6 lines 44d0692c7c55
  4. 2mo ago First seen · 92 lines · 31 tokens per session scan A 40f246d39243

Subscribe to this mod's changes

sqlitecpp-workflow is a skill published in the GitHub repository SRombauts/SQLiteCpp (2,808 stars, last pushed 14d ago), licensed MIT. It adds 31 tokens to every session and 1,442 once invoked, about $0.0001 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-08-30.

Git and workflow
Related

sqlitecpp-workflow compared with skills from other repositories

sqlitecpp-workflow next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sqlitecpp-workflowSRombauts/SQLiteCppSkill2.8k14d agoMITA31Claude Code
merge-batchdiegosouzapw/OmniRouteSkill83k6d agoMITA46Claude Code
prowler-commitprowler-cloud/prowlerSkill15ktodayApache-2.0A44Claude Code, Codex
gh-auth-isolationgithub/gh-awSkill5.6ktodayMITA20Claude Code, Codex
comet-githubrpamis/cometSkill3.3kyesterdayMITA72Claude Code, Codex
github-skillzeenie-ai/OpenCompanySkill1.1k2d agoMITA51Claude Code
release-helperSahir619/fable-methodSkill2.3k1mo agoMITA43Claude Code