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 agentmods add skills/zebbern/termstack/ctf-solvernpx skills add zebbern/termstack --skill ctf-solvergit 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/ctf-solver)<a href="https://agentmods.dev/skills/zebbern/termstack/ctf-solver"><img src="https://agentmods.dev/badge/skills/zebbern/termstack/ctf-solver.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.01684 |
| Opus 5 | $0.00015 | $0.00842 |
| Sonnet 5 | $0.00006 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
ctf-solver scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` for simple HTTP requests 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.
- today First seen · 183 lines · 31 tokens per session scan A 31f4cfe1b17f
ctf-solver is a skill published in the GitHub repository zebbern/termstack (5 stars, last pushed 4mo ago), with no licence file. It adds 31 tokens to every session and 1,684 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (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
auto-devflow
Use when starting an issue, bugfix, feature, or refactor that benefits from an adaptive development workflow. Select lite, normal, pro, max, or ultra from task complexity and risk, then use only the coordination, review, and verification phases that the task actually needs.
langfuse
Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any…
heavy-verify-loop
Runs a user-level verification and repair loop against the real Peri TUI using ./dev.sh, tmux, logs, E2E helpers, and Advisor/Coder/Reviewer subagents. Use when a feature must be exercised as a real user and repeatedly repaired until fresh end-to-end evidence shows no blocking problems.
learn-from-history
审计近期对话历史，提炼重复失败、成功模式、稳定规则和 skill 改进。用户要求总结历史对话、 回顾近期 agent 表现、从历史中学习或寻找可自动化改进时使用。.
programmatic-tool-calling
Use programmatic tool calling to discover extra tools, compose multiple tool calls in ESM code, and return a compact JSON-compatible result.
debugging
用科学方法定位 bug 的根因，而不是凭直觉乱改碰运气。核心：调试是观察 → 假设 → 设计实验验证 → 缩小范围 → 定位根因的循环，每一步都有依据。改到"不报错"不算修好——那可能只是把症状盖住了，根因还在。.