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/st0ff3l/fileterm/fileterm-releasenpx skills add St0ff3l/fileterm --skill fileterm-releasegit clone --depth 1 https://github.com/St0ff3l/filetermWrote 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/st0ff3l/fileterm/fileterm-release)<a href="https://agentmods.dev/skills/st0ff3l/fileterm/fileterm-release"><img src="https://agentmods.dev/badge/skills/st0ff3l/fileterm/fileterm-release.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.00087 | $0.02565 |
| Opus 5 | $0.00044 | $0.01282 |
| Sonnet 5 | $0.00017 | $0.00513 |
| Haiku 4.5 | $0.00009 | $0.00257 |
Grade A, and why
fileterm-release 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 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.
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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FileTerm GitHub Release
目标
把 FileTerm 的版本发布拆成两部分：
- 自定义正文：版本简介、更新重点、主要 PR/Issue、使用提示和反馈渠道。
- GitHub 官方生成区：
What's Changed、New Contributors、Full Changelog、贡献者头像和贡献者展示。
自定义正文只负责第一部分，绝不能手写或覆盖第二部分。
必须先读取
进入仓库后先读取：
AGENTS.mddocs/quality/git-branch-release-convention.md.github/workflows/release.yml- 目标版本对应的
docs/release-notes/release-notes-<version>.md（如果已经存在）
以仓库文件为准，不要凭记忆替换发布命令、分支规则或版本同步方式。
标准流程
1. 在普通分支完成版本说明和版本号
- 功能、修复、文档和版本号改动先进入普通分支并提 PR 到
main。 - 版本号只修改根目录
package.json的version字段。 - 修改后立即运行
npm run sync:version，再检查 workspace 版本和 lockfile。 - 发布说明文件应在合入
main前进入 PR，并统一放在docs/release-notes/，例如：docs/release-notes/release-notes-2.2.0-beta.1.md。 - 不要把日常功能改动直接推到
main或release/*。
2. 发布说明正文格式
推荐结构：中文正文、英文正文、GitHub 官方生成区。中文和英文都属于自定义正文，英文版本紧跟在中文版本后面；官方生成区必须由 GitHub 在最后追加。
以下标题属于固定格式，必须原样保留，不得改写成“相关 Pull Request”“本版本包含的主要 PR”或其他近义标题：中文使用 ### 本版本包含的主要 PR 和问题修复、### 反馈与支持，英文使用 ### Main PRs and issues、### Feedback & Support。
### 反馈与支持 以及其下的两段中文正文、空行和链接组成一个逐字固定块，必须整体复制，不得改写、拆分、改成列表或替换链接：
### 反馈与支持
遇到问题请前往 [GitHub Issues](https://github.com/St0ff3l/fileterm/issues) 提交反馈，并附上操作系统、FileTerm 版本、连接类型、复现步骤和脱敏日志；不要提交密码、私钥或 token。
也可以打开仓库 [README 的“社区交流”部分](https://github.com/St0ff3l/fileterm#%E7%A4%BE%E5%8C%BA%E4%BA%A4%E6%B5%81) 加入社区。
## FileTerm <version>
一句话版本简介。
### <version> 更新重点
- **功能主题**：用户能感知的变化和边界。
- **稳定性/兼容性**：平台或核心链路变化。
- **安全与隐私**：数据发送、权限、凭据和人工确认边界。
### 本版本包含的主要 PR 和问题修复
- [PR #123](https://github.com/St0ff3l/fileterm/pull/123)：简要说明。
- [Issue #456](https://github.com/St0ff3l/fileterm/issues/456)：简要说明。
完整变更记录请查看 [v<old> 与 v<version> 的比较](https://github.com/St0ff3l/fileterm/compare/v<old>...v<version>)。
### 反馈与支持
遇到问题请前往 [GitHub Issues](https://github.com/St0ff3l/fileterm/issues) 提交反馈，并附上操作系统、FileTerm 版本、连接类型、复现步骤和脱敏日志；不要提交密码、私钥或 token。
也可以打开仓库 [README 的“社区交流”部分](https://github.com/St0ff3l/fileterm#%E7%A4%BE%E5%8C%BA%E4%BA%A4%E6%B5%81) 加入社区。
---
## FileTerm <version>
One-sentence release summary in English.
### Highlights
- **Feature theme**: Describe the user-visible change and its boundaries.
- **Stability and compatibility**: Describe platform or core workflow changes.
- **Security and privacy**: Describe data scope, permissions, credentials, and confirmation boundaries.
### Main PRs and issues
- [PR #123](https://github.com/St0ff3l/fileterm/pull/123): Short description.
- [Issue #456](https://github.com/St0ff3l/fileterm/issues/456): Short description.
See the [comparison between v<old> and v<version>](https://github.com/St0ff3l/fileterm/compare/v<old>...v<version>) for the complete change set.
### Feedback & Support
For problems, open a [GitHub Issue](https://github.com/St0ff3l/fileterm/issues) with the operating system, FileTerm version, connection type, reproduction steps, and redacted logs. Do not submit passwords, private keys, or tokens.
Join the community through the [README community section](https://github.com/St0ff3l/fileterm#%E7%A4%BE%E5%8C%BA%E4%BA%A4%E6%B5%81).
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 Changed ed354bf32b20
- 4d ago First seen · 197 lines · 87 tokens per session scan A 9780c69edaaf
fileterm-release is a skill published in the GitHub repository St0ff3l/fileterm (301 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 2,565 once invoked, about $0.0004 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-30.
Other skills, from other repositories
livecodes/framework-wrappers
Use SDK with React, Vue, Svelte, Solid, Preact, and Web Components. sdkReady callback pattern, reactive props, and framework-specific setup. Load this skill when embedding LiveCodes in a framework application.
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
flags
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.