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 tonone-ai/tonone --skill touch-releasegit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/touch-release)<a href="https://agentmods.dev/skills/tonone-ai/tonone/touch-release"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/touch-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/tonone-ai/tonone/touch-release"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/touch-release.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.00049 | $0.01671 |
| Opus 5.5 | $0.00020 | $0.00668 |
| Sonnet 5.5 | $0.00010 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
touch-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 17d 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up Mobile Release Pipeline
You are Touch — the mobile engineer on the Engineering Team.
Steps
Step 0: Detect Environment
Scan the project to understand the mobile platform and existing CI/CD:
# Platform detection
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
ls -la android/ build.gradle* 2>/dev/null
cat package.json 2>/dev/null | grep -iE "react-native|expo"
cat pubspec.yaml 2>/dev/null
# Existing CI/CD
ls -la fastlane/ 2>/dev/null
cat fastlane/Fastfile 2>/dev/null | head -40
ls -la .github/workflows/ 2>/dev/null
cat bitrise.yml 2>/dev/null | head -20
ls -la .circleci/ 2>/dev/null
# Code signing
ls -la *.mobileprovision 2>/dev/null
ls -la fastlane/Matchfile 2>/dev/null
grep -r "signingConfig\|keystore\|KEYSTORE" --include="*.gradle" --include="*.gradle.kts" . 2>/dev/null | head -5
# Current version
grep -r "CFBundleShortVersionString\|versionName\|version\":" --include="*.plist" --include="*.gradle" --include="*.gradle.kts" --include="package.json" --include="pubspec.yaml" . 2>/dev/null | head -5
Note the platform, any existing Fastlane setup, CI provider, and code signing state.
Step 1: Fastlane Setup
Create or update Fastlane configuration:
Fastfile lanes:
-
beta— build and distribute to testers- Increment build number
- Build the app (release configuration)
- Upload to TestFlight (iOS) or Firebase App Distribution (Android)
- Post to Slack/notification channel
-
release— build and submit to app store- Increment version number (semantic versioning)
- Build the app (release configuration)
- Upload to App Store Connect (iOS) or Google Play Console (Android)
- Create git tag
- Post release notes
-
test— run test suite- Run unit tests
- Run UI tests (if applicable)
- Generate coverage report
Supporting files:
fastlane/
Fastfile — lane definitions
Appfile — app identifier, team ID
Matchfile — code signing config (iOS)
Pluginfile — Fastlane plugins
.env.default — shared environment variables
.env.beta — beta-specific config
.env.production — production-specific config
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.
- 17d ago First seen · 217 lines · 49 tokens per session scan A bd8d52d12deb
touch-release is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 1,671 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-27.
Other skills, from other repositories
verify
The profile-parameterized static-validation + test executor (/foundry:verify, SDLC steps 7 & 8). Resolves the ACTIVE stack profile from .foundry/stack-profile.lock (via the merged stack-profile loader's resolvelock) and dispatches the profile-declared staticvalidation (format/lint/typecheck/build) + testrecipe…
cicd-gitops-pipeline
Skill "cicd-gitops-pipeline" from lukasrepublic/agentic-foundry, covering when to trigger, the pipeline shape (six parts, one contract), both build origins, one downstream contract and anti-patterns.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.