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 rules/usekaneo/kaneo/database-schemagit clone --depth 1 https://github.com/usekaneo/kaneoWhat 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.00000 | $0.01740 |
| Opus 5 | $0.00000 | $0.00870 |
| Sonnet 5 | $0.00000 | $0.00348 |
| Haiku 4.5 | $0.00000 | $0.00174 |
Grade A, and why
database-schema 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 yesterday.
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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Schema Guidelines
Kaneo uses Drizzle ORM with PostgreSQL. This document outlines schema conventions and best practices.
Schema Definition
All schemas are defined in apps/api/src/database/schema.ts:
import { pgTable, text, timestamp, boolean, integer, index } from "drizzle-orm/pg-core";
import { createId } from "@paralleldrive/cuid2";
export const taskTable = pgTable(
"task",
{
id: text("id")
.$defaultFn(() => createId())
.primaryKey(),
projectId: text("project_id")
.notNull()
.references(() => projectTable.id, {
onDelete: "cascade",
onUpdate: "cascade",
}),
title: text("title").notNull(),
description: text("description"),
status: text("status").notNull().default("to-do"),
createdAt: timestamp("created_at", { mode: "date" }).defaultNow().notNull(),
updatedAt: timestamp("updated_at", { mode: "date" })
.defaultNow()
.$onUpdate(() => new Date())
.notNull(),
},
(table) => [
index("task_projectId_idx").on(table.projectId),
],
);
Naming Conventions
- Table names: Use singular, lowercase with underscores:
task,workspace_user - Column names: Use snake_case:
project_id,created_at,updated_at - Index names: Format:
{table}_{column}_idx - Foreign key columns: End with
_id:project_id,user_id
// Good: Consistent naming
export const workspaceUserTable = pgTable("workspace_user", {
id: text("id").primaryKey(),
workspaceId: text("workspace_id").notNull(),
userId: text("user_id").notNull(),
role: text("role").notNull(),
});
// Bad: Inconsistent naming
export const workspaceUserTable = pgTable("WorkspaceUsers", {
ID: text("ID").primaryKey(),
workspace: text("workspace").notNull(),
user: text("user").notNull(),
});
Required Fields
Every table should include:
- Primary Key:
idfield using CUID2 - Timestamps:
created_atandupdated_atwith proper defaults - Foreign Keys: Proper references with cascade options
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.
- yesterday First seen · 295 lines · 0 tokens per session scan A 553718148689
database-schema is a cursor rule published in the GitHub repository usekaneo/kaneo (8,786 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,740 tokens. 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.
Other cursor rules, from other repositories
no-co-author-in-commits
Do not add or keep Co-authored-by trailers in commit messages.
no-mvn-compile
Do not run mvn compile; rely on IDE lint errors.
git-and-monorepo
Commit message convention and pnpm/Nx monorepo rules.
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
clawsweeper
Triage and process the Slate v2 issue ledger with OpenClaw-style sweep discipline: archive-first discovery, duplicate proof, small-fix gates, exact claim rules, maintainer-safe issue output, and gitcrawl API refreshes.
slate-ar-status
Read-only status shortcut for Slate v2 Autoresearch. Shows current session state, dashboard URL, next recommended action, blockers, and latest metric evidence without running packets or editing files.