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 zebbern/termstack --skill state-persistencegit clone --depth 1 https://github.com/zebbern/termstackWrote 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/zebbern/termstack/state-persistence)<a href="https://agentmods.dev/skills/zebbern/termstack/state-persistence"><img src="https://agentmods.dev/badge/skills/zebbern/termstack/state-persistence/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/zebbern/termstack/state-persistence"><img src="https://agentmods.dev/badge/skills/zebbern/termstack/state-persistence.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.00040 | $0.04436 |
| Opus 5.5 | $0.00016 | $0.01774 |
| Sonnet 5.5 | $0.00008 | $0.00887 |
| Haiku 4.5 | $0.00004 | $0.00444 |
Grade A, and why
state-persistence 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 475 lines · 40 tokens per session scan A bb2833ee139a
state-persistence is a skill published in the GitHub repository zebbern/termstack (4 stars, last pushed 6mo ago), with no licence file. It adds 40 tokens to every session and 4,436 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
ultra-adlc
End-to-end delivery orchestration for explicitly requested, very large software changes that must be completely implemented and independently proven. Use when the user invokes "ultra-adlc" or asks for an Ultra-ADLC-scale full delivery; do not use for ordinary features, small fixes, reviews, or ad hoc parallel work.
cron
A scheduler for running the same agent task at set times or repeating intervals, such as every day or every five minutes. It uses the standard five-part cron schedule format.
repo-checkpoint
Cross-agent repo-local progress checkpoint workflow for any git repository. Use this skill whenever the user says save progress, checkpoint, snapshot the current lane, capture key chat context, write down what matters before closing, or wants the next session to resume immediately from Codex, Claude Code, opencode, or…
clarifying-questions
A requirements-clarification guide for situations where a request is vague, hides important assumptions, or may ask for the wrong solution.
debugging
A methodical way to find the underlying cause of software bugs by observing what happens, forming hypotheses, and testing them. It separates finding the cause from applying and checking the fix.
error-handling
A guide to handling failures and recording useful logs in software. It explains when to pass an error upward, handle it locally, or retry it.