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 retest-vulngit 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/retest-vuln)<a href="https://agentmods.dev/skills/zebbern/termstack/retest-vuln"><img src="https://agentmods.dev/badge/skills/zebbern/termstack/retest-vuln/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/retest-vuln"><img src="https://agentmods.dev/badge/skills/zebbern/termstack/retest-vuln.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.00041 | $0.05108 |
| Opus 5.5 | $0.00016 | $0.02043 |
| Sonnet 5.5 | $0.00008 | $0.01022 |
| Haiku 4.5 | $0.00004 | $0.00511 |
Grade C, and why
retest-vuln scanned grade C 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 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.
Cloud metadata endpointhighServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
{"url": "http://169.254.169.254/latest/meta-data/"} Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://target.com/version | grep -i version 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 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.
- 1mo ago First seen · 741 lines · 41 tokens per session scan C 8713e6f8238f
retest-vuln is a skill published in the GitHub repository zebbern/termstack (4 stars, last pushed 6mo ago), with no licence file. It adds 41 tokens to every session and 5,108 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (cloud metadata endpoint, makes network calls). 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.
verification-loop
Evidence-before-assertions workflow. Use before claiming work is done, before release, and after any behavior change in scripts/skills/MCP.
codexkit-test-hardening
Strengthen test coverage around changed behavior, edge cases, and regressions without writing noisy or brittle tests.
testing
A guide to writing tests that check what software should do rather than how its code is arranged. Tests are repeatable checks; it covers functions, external services, user interfaces, and cooperating modules.
visual-verification
Use for any UI/web project — make the verify gate cover more than unit tests by composing a pipeline (types → unit → design-scan → flow-smoke) and running the built-in yoke flow-smoke gate (landmark + zero console errors + screenshot proof to .yoke/proof/ /, video kept on failure). Catches the unwired-page /…
verify-and-fix
A verification-and-repair workflow for checking finished code with tests, type checks, or a real run of the target scenario. It treats verification as evidence that the work is complete.