todox: Skill for Claude Code

.claude/skills/db-change/SKILL.md

db-change is a skill for Claude Code from beydemirfurkan/todox. It costs 45 tokens per session (968 once invoked), scanned A, original, MIT.

A set of rules for changing the todox application's SQL database code and data-access modules.

In plain words
What is it for?
Use it when writing SQL, changing tables or columns, or editing database and repository code.
Why use it?
It helps avoid SQL injection, broken query parameters, duplicated ownership checks, and misplaced cross-table logic.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is beydemirfurkan/todox's own configuration. It tells Claude Code how to work on todox 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 todox configures →

Reuse

Borrowing it

Nothing to install: this file belongs to beydemirfurkan/todox. 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/beydemirfurkan/todox/main/.claude/skills/db-change/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/beydemirfurkan/todox

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 db-change

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/beydemirfurkan/todox/db-change"><img src="https://agentmods.dev/badge/skills/beydemirfurkan/todox/db-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 968 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.
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.00045 $0.00968
Opus 5 $0.00023 $0.00484
Sonnet 5 $0.00009 $0.00194
Haiku 4.5 $0.00005 $0.00097

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

Security

Grade A, and why

db-change 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 10d 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/db-change/SKILL.md · 92 lines

How it starts

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

Touching the database

No ? inside a SQL string literal

lib/db/client.ts rewrites ? to $n positionally. It does not parse strings, so a question mark inside a quoted literal shifts every parameter after it.

-- wrong: the literal eats a placeholder slot
WHERE note = 'why?' AND user_id = ?

Never build a SET clause by hand

Use setClause(patch, COLUMNS) from lib/db/client.ts. Column names cannot be bound as parameters, so they are interpolated — and patches arrive from const { id, ...patch } = params at the RPC boundary. Iterating the patch's own keys put caller-chosen text into the statement. That was a live SQL injection. The allow-list is the fix; do not route around it.

One module per table

  • lib/repositories/ — one file per table, no cross-table logic.
  • Repositories never call each other. Anything that must stay consistent across tables — a status change writing a task_events row — belongs in lib/services/.

Ownership is checked in exactly one place

lib/services/ownership.ts. Do not inline WHERE user_id = ? at a call site and consider it handled. A row belonging to somebody else answers 404, never 403 and never "not found for you": the message must not tell a caller that an id exists.

Load in batches

The database is over the network. A per-row query inside a list is a per-row round trip — use the listByTasks-style helpers.

Schema and migrations

  • The schema lives in lib/db/schema.ts and is idempotent.
  • pnpm db:migrate is a deploy step, run deliberately. It does not run on cold start: DDL racing across serverless instances is a bad way to discover lock contention.
  • Nothing queries the database at build time — every page is force-dynamic, which is what keeps CI free of secrets.
  • statements() splits SCHEMA on ; and strips -- comments after the split. So a semicolon inside a comment cuts it in half and the rest of the sentence arrives as a statement, and a DO $$ … $$ block cannot be expressed here at all — its body has semicolons in it.

Read the full file on GitHub · 92 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. 10d ago First seen · 92 lines · 45 tokens per session scan A 245c704d4f5c

Subscribe to this mod's changes

db-change is a skill published in the GitHub repository beydemirfurkan/todox (2 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 968 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

cmdb-patterns

Create ServiceNow CIs and cmdbrelci relationships, walk upstream/downstream impact, detect orphan/stale CIs, and align discovered CIs with the proper sysclassname hierarchy.

serac-labs/serac · 43 tokens

data-policies

Manage ServiceNow dictionary (sysdictionary), table/field creation, choice lists, dictionary overrides, and sysdatapolicy2 rules that enforce mandatory/read-only/visible field behavior on the data layer.

serac-labs/serac · 43 tokens

import-export

Move data in and out of ServiceNow — CSV parsing into import sets, GlideImportSetTransformer runs, CSV/JSON/XML exports, scheduled data sources, bulk update and deleteMultiple safety patterns.

serac-labs/serac · 42 tokens

gliderecord-patterns

Write efficient ServiceNow GlideRecord queries — addQuery vs addEncodedQuery, setLimit, GlideAggregate for counts, avoiding N+1 in loops, query operators, and safe CRUD with workflow control.

serac-labs/serac · 46 tokens

sqlike

Check SQL with sqlike — deterministic static analysis (validity, anti-patterns, rewrites, index advice) and query-equivalence verification. Use whenever you write, edit, review, or rewrite a SQL query, or need to prove two queries return the same results. Requires the sqlike MCP server (@sqlike/mcp) or the sqlike CLI…

orifisher2/sqlike · 81 tokens

supabase-schema-generator

An SRE-grade automation skill to parse SQL schemas and auto-generate safe TypeScript interfaces for the frontend and Row Level Security (RLS) policies for Supabase.

aragaobruno/toolbelt · 0 tokens