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-deploy-and-runtimegit 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-deploy-and-runtime)<a href="https://agentmods.dev/skills/adtn0810/truestack/truestack-deploy-and-runtime"><img src="https://agentmods.dev/badge/skills/adtn0810/truestack/truestack-deploy-and-runtime/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-deploy-and-runtime"><img src="https://agentmods.dev/badge/skills/adtn0810/truestack/truestack-deploy-and-runtime.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.00231 | $0.02184 |
| Opus 5 | $0.00115 | $0.01092 |
| Sonnet 5 | $0.00046 | $0.00437 |
| Haiku 4.5 | $0.00023 | $0.00218 |
Grade D, and why
truestack-deploy-and-runtime scanned grade D with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Keep the real secret file **outside the repo, `chmod 600`, owned by the deploy user, `.gitignore`d**. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
destructive shell/MCP ops it classifies (`docker volume rm`, `rm -rf`, `git reset --hard`, a DB How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
truestack-deploy-and-runtime
Get the app onto one box and keep it serving through every deploy, cert rotation, and reboot. One server, fixed resources, no autoscale — so "low-downtime" is a connection-draining reload, never a restart, and every change has a sub-second rollback ready before it ships. Stability over cleverness; a deploy that can't roll back isn't done.
Read project memory first — CLAUDE.md is auto-loaded (Principles + Boundaries); consult
.ai/memory/ for the deploy commands, ports, domains, and ops decisions already recorded.
If none exists, run truestack-project-memory. A deploy, image, or cert change is high-risk and
irreversible-shaped — route the plan through truestack-architecture-planning's approval gate before
touching the live box, and know the enforced PreToolUse gate in hooks/ asks before the
destructive shell/MCP ops it classifies (docker volume rm, rm -rf, git reset --hard, a DB
migration) until a human approves.
Where this skill sits: the app/server logic is truestack-backend-development; this skill packages and
runs that app on the box. The CI workflow that triggers this deploy is truestack-ci-and-delivery; the
migration DDL it runs is truestack-database-migrations; the app's instrumentation/SLO signal is
truestack-observability (this skill owns the container/compose healthcheck and the cutover readiness gate).
1. Make SIGTERM reach the app, then handle it
The #1 silent failure: shell-form CMD node server.js makes /bin/sh PID 1, which swallows
SIGTERM — Docker waits the full grace period then SIGKILLs mid-request. Fixes:
- Exec form
CMD ["node","server.js"](orinit: true/ tini if you need an entrypoint wrapper) so the app is PID 1 and actually receives the signal. - Trap SIGTERM and drain in order: (1) flip readiness to failing so the proxy stops routing, (2)
server.close()to finish in-flight requests, (3) close DB pools, (4) hard-exit on a bounded timeout. - Set
stop_grace_periodLONGER than that timeout — the 10s default is almost always too short and truncates a clean drain into a kill.
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 · 111 lines · 231 tokens per session scan D 593405369af5
truestack-deploy-and-runtime is a skill published in the GitHub repository adtn0810/truestack (2 stars, last pushed 2mo ago), licensed MIT. It adds 231 tokens to every session and 2,184 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deploy-gen
Generate deployment configurations (Docker, Kubernetes) for the current project.
docker-devops
Docker/K8s: Dockerfile, multi-stage, compose, manifests, Helm. Triggers: Docker, Dockerfile, container, Kubernetes, k8s, compose, Helm, pod.
health
Service/infra health via liveness/readiness checks, resource usage, quick diagnostics. Triggers: health check, services up, system status, infra health, degraded service.
software-paas-hosting
Chooses PaaS compute hosting for apps, agents, bots, APIs, and workers. Use when picking Vercel, Fly.io, Railway, Render, Cloudflare, Deno, or container PaaS.
edge-computing-expert
Design and implement production-grade edge computing solutions including CDN optimization, fog computing architectures, and distributed edge workloads. Use when the user mentions edge computing, CDN or edge caching, fog computing, MEC, IoT edge workloads, or latency-sensitive distributed deployments.
vllm-deployment
Use this skill when authoring, reviewing, or fixing a vLLM Kubernetes manifest, Docker/Podman pod, or OpenShift ServingRuntime — even when the user does not say "vllm". Triggers on: lab cluster performance practices, cache mount + survival across pod restarts (/root/.cache, VLLMCACHEROOT, TORCHINDUCTORCACHEDIR…