Borrowing it
Nothing to install: this file belongs to truss-harness/Truss. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/truss-harness/Truss/master/.skills/truss-storage-layer/SKILL.mdgit clone --depth 1 https://github.com/truss-harness/TrussWrote 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.
[](https://agentmods.dev/skills/truss-harness/truss/truss-storage-layer)<a href="https://agentmods.dev/skills/truss-harness/truss/truss-storage-layer"><img src="https://agentmods.dev/badge/skills/truss-harness/truss/truss-storage-layer/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.
<a href="https://agentmods.dev/skills/truss-harness/truss/truss-storage-layer"><img src="https://agentmods.dev/badge/skills/truss-harness/truss/truss-storage-layer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00087 | $0.00664 |
| Opus 5 | $0.00044 | $0.00332 |
| Sonnet 5 | $0.00017 | $0.00133 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
truss-storage-layer 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 9d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Truss Storage Layer
Use this skill before changing Truss persistence, configuration, or settings APIs.
Core Rules
- Keep secrets out of SQLite. Provider API keys belong in the dotenvx-backed
~/.truss/.env; private key material belongs in~/.truss/.env.keys. - Access SQLite through repository modules in
src/server/storage/**. Do not write SQL directly in agents, route handlers, or UI code. - Put schema changes in
src/server/storage/migrations.tsas a new numbered migration. Do not edit already-applied migration SQL unless the existing migration is known to be unreleased and disposable. - Keep protocol payloads sanitized. Never return API keys, OAuth tokens, dotenvx values, or raw process env values to the frontend.
- Keep provider/model identity explicit as
providerIdplusmodelId; do not serialize provider/model as one ambiguous string. - Snapshot provider/model/generation parameters into
agent_sessionswhen a session is created. Later profile changes should not silently rewrite historical session metadata. - Enforce sub-agent hierarchy through storage constraints: only
sub-agentsessions haveparentSessionId, and they must have one. - Keep agentic tool turn limit settings on the
rich_feature_settingssingleton:agentic_tool_turn_limit_enabledandagentic_tool_turn_limit, defaulting to enabled and 300.
Workflow
- Read
docs/database-schema.mdbefore changing tables, indexes, or repository query patterns. - Search repository methods for the affected tables before deciding on columns or indexes.
- Add or update migration SQL, then update the matching repository module.
- Update
src/shared/protocol.tsonly with sanitized fields needed by browser/API clients. - Update HTTP route validation before accepting new browser-provided fields.
- Update
docs/database-schema.mdwhen schema, constraints, indexes, or query patterns change. - Validate with
bun run check; for schema/index work, also create a temporary SQLite DB and inspectPRAGMA index_list(...).
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 44 lines · 87 tokens per session scan A 03354545641d
truss-storage-layer is a skill published in the GitHub repository truss-harness/Truss (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 664 once invoked, about $0.0004 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
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…