spekka: Skill for Claude Code

.claude/skills/spekka-backend-models/SKILL.md

Backend Models is a skill for Claude Code from johnreitano/spekka. It costs 24 tokens per session (217 once invoked), scanned A, original, MIT.

Guidance for designing backend data models, the code and database structures that represent application data.

In plain words
What is it for?
It is for naming models and tables, choosing data types, adding timestamps and indexes, defining relationships, and enforcing database constraints.
Why use it?
It helps protect data quality and keep database relationships, validation, and queries predictable.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

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

Reuse

Borrowing it

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

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 Backend Models

README.md
[![agentmods](https://agentmods.dev/badge/skills/johnreitano/spekka/spekka-backend-models/github.svg)](https://agentmods.dev/skills/johnreitano/spekka/spekka-backend-models)
Your own site
<a href="https://agentmods.dev/skills/johnreitano/spekka/spekka-backend-models"><img src="https://agentmods.dev/badge/skills/johnreitano/spekka/spekka-backend-models/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 Backend Models

Your own site · 80×15
<a href="https://agentmods.dev/skills/johnreitano/spekka/spekka-backend-models"><img src="https://agentmods.dev/badge/skills/johnreitano/spekka/spekka-backend-models.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 217 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.00024 $0.00217
Opus 5 $0.00012 $0.00109
Sonnet 5 $0.00005 $0.00043
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

Backend Models 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/spekka-backend-models/SKILL.md · 20 lines

What it actually says

Backend Models

This Skill provides Claude Code with specific guidance on how it should handle backend models.

Instructions

  • Clear Naming: Use singular names for models and plural for tables following your framework's conventions
  • Timestamps: Include created and updated timestamps on all tables for auditing and debugging
  • Data Integrity: Use database constraints (NOT NULL, UNIQUE, foreign keys) to enforce data rules at the database level
  • Appropriate Data Types: Choose data types that match the data's purpose and size requirements
  • Indexes on Foreign Keys: Index foreign key columns and other frequently queried fields for performance
  • Validation at Multiple Layers: Implement validation at both model and database levels for defense in depth
  • Relationship Clarity: Define relationships clearly with appropriate cascade behaviors and naming conventions
  • Avoid Over-Normalization: Balance normalization with practical query performance needs
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 · 20 lines · 24 tokens per session scan A 7af4daae3376

Subscribe to this mod's changes

Backend Models is a skill published in the GitHub repository johnreitano/spekka (5 stars, last pushed 8mo ago), licensed MIT. It adds 24 tokens to every session and 217 once invoked, about $0.0001 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

event-store-design

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

wshobson/agents · 33 tokens

convex-explain-app

Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.

openclaw/clawhub · 47 tokens

platform-custom-field-generate

Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…

forcedotcom/sf-skills · 194 tokens

field-service-sobject-create-configure

Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…

forcedotcom/sf-skills · 74 tokens

openloomi-api

OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…

melandlabs/openloomi · 106 tokens

nornicdb-grpc

Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…

orneryd/NornicDB · 98 tokens