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 skills/neverinfamous/memory-journal-mcp/drizzle-ormnpx skills add neverinfamous/memory-journal-mcp --skill drizzle-ormgit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWhat 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.00065 | $0.00711 |
| Opus 5 | $0.00032 | $0.00356 |
| Sonnet 5 | $0.00013 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
drizzle-orm 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 3d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drizzle ORM Guidelines
This skill provides opinionated standards for using Drizzle ORM, optimized for TypeScript and edge databases like Cloudflare D1.
1. Core Principles
- Single Source of Truth: Define your database schema in TypeScript. Let Drizzle generate the SQL migrations.
- Explicit Returns: Always explicitly select the columns you need using
.select({ id: table.id }). Avoidselect *in production queries to minimize payload size and improve performance. - Relational Queries: Use Drizzle's Relational Query API (
db.query) for complex joined data fetching, but use the Core API (db.select().from()) for mutations and simple lookups. - Type Inference: Use
typeof schema.table.$inferSelectand$inferInsertto generate application types directly from the schema.
2. Schema Definition
Always define schemas with precise types and constraints.
import { sqliteTable, text, integer } from 'drizzle-orm/sqlite-core'
export const users = sqliteTable('users', {
id: integer('id').primaryKey({ autoIncrement: true }),
email: text('email').notNull().unique(),
name: text('name').notNull(),
createdAt: integer('created_at', { mode: 'timestamp' })
.notNull()
.$defaultFn(() => new Date()),
})
export type User = typeof users.$inferSelect
export type NewUser = typeof users.$inferInsert
3. Querying Patterns
Inserts and Returning
const result = await db
.insert(users)
.values({ email: '[email protected]', name: 'Test' })
.returning() // Supported in D1
Relational Queries (Read-Heavy)
Ensure you define relations in your schema file:
export const usersRelations = relations(users, ({ many }) => ({
posts: many(posts),
}))
Fetch deeply nested data easily:
const userWithPosts = await db.query.users.findFirst({
where: eq(users.id, 1),
with: {
posts: true,
},
})
4. Migrations (Cloudflare D1)
Always generate migrations locally and apply them via Wrangler. Never execute db.execute() with raw migration SQL at runtime.
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.
- 3d ago First seen · 83 lines · 65 tokens per session scan A 6d963d8ed86d
drizzle-orm is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 711 once invoked, about $0.0003 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-30.
Other skills, from other repositories
mie-generator
Generate or update MIE (Metadata Interoperability Exchange) YAML files that describe RDF databases for TogoMCP. Use this skill whenever the user asks to create, write, regenerate, update, or improve an MIE file for any RDF database (UniProt, ChEMBL, Reactome, Rhea, PubChem, MeSH, PDB, or any new bio/chem database…
guardian-cache
Store temporary agent state and cached API results in Redis using enforced mema: namespaces and TTL controls. Use when session data or expensive intermediate results must be shared across steps or sub-agents.
nextcloud-ingest
Natively ingest Nextcloud files into the epistemic-graph knowledge graph via the nextcloud-agent MCP server — fetch a file over WebDAV and store its raw bytes as a content-addressed :Blob/:AssetOccurrence plus its extracted text (pdf/office/txt or image OCR) as a linked :Document. Use when the agent must make a…
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.