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/zachjxyz/jvn/stack-knowledgenpx skills add zachjxyz/jvn --skill stack-knowledgegit clone --depth 1 https://github.com/zachjxyz/jvnWhat 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.00026 | $0.00921 |
| Opus 5 | $0.00013 | $0.00461 |
| Sonnet 5 | $0.00005 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
stack-knowledge 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 2d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack Knowledge
This skill provides stack-specific patterns for agents making architectural and implementation decisions.
FastAPI
- Async route handlers by default — use
async deffor all endpoints - Dependency injection with
Depends()for database sessions, auth, shared logic - Pydantic V2 models for all request/response schemas — never return raw dicts
- Use
lifespancontext manager for startup/shutdown (DB connections, ML model loading) - Router organization:
src/api/routes/with one router per domain - Error handling:
HTTPExceptionfor expected errors, exception handlers for unexpected - Consistent error shape:
{ "error": str, "message": str, "details": dict } - Background tasks with
BackgroundTasksfor non-blocking operations
PostgreSQL + SQLAlchemy
- SQLAlchemy 2.0 style — use
select(),insert(),update(),delete()statements - Async engine with
create_async_engine()andasync_sessionmaker() - Connection string via
DATABASE_URLenv var - Models in
src/models/with one file per entity - Use
mapped_column()with explicit types — no implicit column inference - Index every column used in WHERE, JOIN, or ORDER BY
- Relationship loading: use
selectinload()for collections,joinedload()for single relations - Session management: request-scoped sessions via
Depends(get_db)
Alembic Migrations
- Config in
alembic.ini, env inalembic/env.py - Development:
alembic revision --autogenerate -m "description" - Production: manually reviewed migrations, never autogenerate blindly
- Always test migrations both up and down (rollback)
- One migration per logical change — don't batch unrelated schema changes
PyTorch / ML
- Models in
src/models/ml/— separate from SQLAlchemy ORM models - Training scripts in
src/training/ - Inference endpoints load models at startup via lifespan, not per-request
- Reproducibility: set seeds (
torch.manual_seed,numpy.random.seed), log hyperparameters - Model versioning: save checkpoints with metadata (epoch, metrics, config)
- Data pipelines in
src/pipelines/— pandas for ETL, torch DataLoaders for training
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.
- 2d ago First seen · 87 lines · 26 tokens per session scan A 4899dc77b57e
stack-knowledge is a skill published in the GitHub repository zachjxyz/jvn (2 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 921 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.
Other skills, from other repositories
cli-audit-data
Audit PostgreSQL database safety in Rust/SQLx applications. Use for schemas, migrations, constraints, indexes, transactions, repositories, state transitions, idempotency, concurrency, queues, multi-tenancy, soft deletion, ledgers, auditability, repair, database incidents, or whenever SQLx and PostgreSQL changes could…
db-context-postgres
Validate that a generic Postgres database (GCP Cloud SQL, GKE Autopilot, self-hosted, etc.) is reachable via psql or pgdump, introspect a user-scoped subset of the schema (extensions, tables, columns, indexes, foreign keys, and optionally RLS policies and functions), and persist the result as DBCONTEXT.md inside the…
db-context-supabase
Validate that a Supabase MCP server is reachable, introspect a user-scoped subset of the database (tables, columns, types, RLS policies, optionally functions and recent migrations), and persist the result as DBCONTEXT.md inside the active task folder; adds a single ## DB context cross-link in SOURCEOFTRUTH.md.…
cli-forge-data
Design and implement safe PostgreSQL database changes for Rust/SQLx applications. Use for new schemas, migrations, constraints, indexes, repositories, transaction boundaries, state machines, idempotency, concurrency control, queues, multi-tenancy, soft deletion, ledgers, outbox/inbox, repair jobs, or corrections…
postgres-pro
Use when optimizing PostgreSQL queries, configuring replication, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, performance monitoring.
PostgreSQL Database
Development patterns with PostgreSQL via FireDAC — connection, PL/pgSQL, sequences, JSONB, UPSERT, full-text search, migrations.