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 termio-sh/termio --skill testflight-releasegit clone --depth 1 https://github.com/termio-sh/termioWrote 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/termio-sh/termio/testflight-release)<a href="https://agentmods.dev/skills/termio-sh/termio/testflight-release"><img src="https://agentmods.dev/badge/skills/termio-sh/termio/testflight-release/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/termio-sh/termio/testflight-release"><img src="https://agentmods.dev/badge/skills/termio-sh/termio/testflight-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 151 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 151 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 68 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 82 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 82 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Privilege Escalation · line 144 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00102 | $0.02585 |
| Opus 5.5 | $0.00041 | $0.01034 |
| Sonnet 5.5 | $0.00020 | $0.00517 |
| Haiku 4.5 | $0.00010 | $0.00259 |
Grade B, and why
testflight-release scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
mkdir -p ~/Library/Developer/asc-signing/termio && chmod 700 ~/Library/Developer/asc-signing/termio How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestFlight release (iOS companion)
Cuts a TestFlight build of TermioMobile by hand. Unlike the Mac app, this is
not automated: .github/workflows has no upload step, so nothing happens when
a PR merges. Every TestFlight build is a local archive + upload.
Use the asc skill for anything beyond this path (crash triage, App Store
submission, metadata). This skill is only the beta-build pipeline, with the
repo-specific facts that asc cannot know.
Constants
| Thing | Value |
|---|---|
| App ID | 6790142237 (sh.termio.mobile, "Termio: Agentic Terminal") |
| Bundle ID resource | 97KQ9JGYL8 |
| Team | 5Y27G7B6D8, from ios/Signing.xcconfig — not the project file |
| Internal group | 7b62f012-b166-40df-ba19-e43c3a0b2c88 |
| Public Beta group | fe170244-643a-4c73-9c94-84ab44c254f9 (external, public link) |
| Signing assets | ~/Library/Developer/asc-signing/termio/ (mode 700, outside the repo) |
The build number in the repo is a lie
CURRENT_PROJECT_VERSION in ios/TermioMobile.xcodeproj/project.pbxproj sits at
an old value (285 at the time of writing) while App Store Connect is in the
700s. That is deliberate: the bump is applied for the archive and then thrown
away.
Never commit the bump. Resolve it against ASC, build, upload, revert:
cd ios
asc xcode version edit --next-build-number --app 6790142237 --platform IOS \
--project TermioMobile.xcodeproj --output json
# ... archive, export, upload ...
git checkout -- TermioMobile.xcodeproj/project.pbxproj
Uploading a build number at or below the highest one in ASC is rejected, so never guess it from the repo.
Steps
Run from a clean worktree on the commit you want to ship (normally main).
-
Bump — the command above. It reports the number it chose.
-
Archive (Release, signed for distribution):
cd ios asc xcode archive \ --project TermioMobile.xcodeproj --scheme TermioMobile \ --configuration Release --clean \ --archive-path .asc/artifacts/TermioMobile.xcarchive \ --xcodebuild-flag=-destination --xcodebuild-flag=generic/platform=iOS \ --xcodebuild-flag=-allowProvisioningUpdates --output json
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 · 215 lines · 102 tokens per session scan B bca67607523f
testflight-release is a skill published in the GitHub repository termio-sh/termio (548 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 2,585 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
release
Cut a new gflow-cli release — bump version, update CHANGELOG, tag, push, and back-merge.
changelog
Show unreleased changes and last tagged version — insight into recent work.
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
flame-harness-submit
Phase 10 — upload store text metadata + categories via fastlane, then pause with exact manual steps for the final iOS review submission and Android production promotion.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.