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 skills add adtn0810/truestack --skill truestack-backend-developmentgit clone --depth 1 https://github.com/adtn0810/truestackWrote 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/adtn0810/truestack/truestack-backend-development)<a href="https://agentmods.dev/skills/adtn0810/truestack/truestack-backend-development"><img src="https://agentmods.dev/badge/skills/adtn0810/truestack/truestack-backend-development/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/adtn0810/truestack/truestack-backend-development"><img src="https://agentmods.dev/badge/skills/adtn0810/truestack/truestack-backend-development.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.00107 | $0.01355 |
| Opus 5 | $0.00053 | $0.00678 |
| Sonnet 5 | $0.00021 | $0.00271 |
| Haiku 4.5 | $0.00011 | $0.00136 |
Grade A, and why
truestack-backend-development 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
truestack-backend-development
Recommend the best stack for this project, then write code that is accurate under load and won't take down a self-hosted VPS. Accuracy and stability beat cleverness.
Read project memory first — CLAUDE.md is auto-loaded (Principles + Boundaries); consult
.ai/memory/ for stack, commands, and conventions. Respect the Ask-first / Never
boundaries. If none exists, run truestack-project-memory.
For a real external action — DB write, vector search, payment, webhook, third-party API —
go through truestack-mcp-integration rather than hand-rolling the call: it carries the
untrusted-data boundary, the money/destructive Ask-first gate, idempotency, and the
verify-the-effect rule.
If the request is ambiguous — more than one reasonable implementation fits — clarify first
with a short, capped round of questions-with-defaults before writing code; don't guess.
(Same clarify-then-proceed loop as truestack-architecture-planning.) Seams: planning a new
build starts in truestack-architecture-planning; authoring schema/data migrations (DDL,
backfills) is truestack-database-migrations, not here.
1. Stack — match the project, recommend only for greenfield
Before recommending or using a library/framework/API, ground it in current docs — auto-research
the version, API surface, and any advisory from authoritative sources (context7 / official docs)
rather than trusting recall (per the always-on contract).
Existing repo: use the language/framework already in use (from memory) — don't switch it.
Greenfield: recommend with a one-paragraph justification tied to accuracy, performance,
and the single-server constraint:
- Node / Express (or Fastify) + TypeScript — I/O-bound APIs, shared types.
- .NET / ASP.NET Core — typed, high-throughput services with a strong EF Core data layer.
- Python / FastAPI — async APIs, data/ML-leaning work.
- Database — Postgres by default for correctness; SQLite for small single-node apps; Redis as cache/queue, not source of truth.
What ships with it
1 file 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.
- 10d ago First seen · 79 lines · 107 tokens per session scan A 5e4d8129ab2f
truestack-backend-development is a skill published in the GitHub repository adtn0810/truestack (2 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 1,355 once invoked, about $0.0005 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
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
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.
gemini-api-agent-platform
Guides the usage of the Gemini API on Agent Platform with the Google Gen AI SDK for enterprise AI applications. Covers SDK usage (Python, JS/TS, Go, Java, C#), capabilities like Live API, tools, multimedia generation, caching, and batch prediction.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.