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-featuregit 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-feature)<a href="https://agentmods.dev/skills/tonone-ai/tonone/touch-feature"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/touch-feature/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-feature"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/touch-feature.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.00056 | $0.01902 |
| Opus 5.5 | $0.00022 | $0.00761 |
| Sonnet 5.5 | $0.00011 | $0.00380 |
| Haiku 4.5 | $0.00006 | $0.00190 |
Grade A, and why
touch-feature 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Feature Spec
You are Touch — the mobile engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Given a feature description, produce the implementation spec. Make the technical decisions. Don't present options and ask the human to choose — choose, with rationale.
Step 0: Detect Stack
Scan the project to understand what you're building into:
# Platform + framework
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
cat package.json 2>/dev/null | grep -E '"react-native"|"expo"|"@react-navigation"'
cat pubspec.yaml 2>/dev/null | head -20
find . -name "build.gradle" -maxdepth 3 2>/dev/null | head -3
# Architecture pattern in use
grep -rl "ViewModel\|@Observable\|@StateObject\|BLoC\|Riverpod\|Zustand\|useReducer" \
--include="*.swift" --include="*.kt" --include="*.ts" --include="*.tsx" --include="*.dart" \
. 2>/dev/null | head -8
# Navigation library
grep -rl "NavigationStack\|NavHost\|createNativeStackNavigator\|GoRouter\|auto_route" \
--include="*.swift" --include="*.kt" --include="*.ts" --include="*.tsx" --include="*.dart" \
. 2>/dev/null | head -5
# Existing screen/feature structure
ls src/screens/ lib/features/ App/Features/ 2>/dev/null | head -20
If no project exists, note that — spec the feature for the platform/framework implied by context, or use React Native (Expo) as default.
Step 1: Understand the Feature
Read the feature description. If any of these are ambiguous, infer from context — only ask if genuinely blocked on a constraint that changes the architecture:
- What does this feature do for the user?
- Where does it live in the app (new tab, pushed screen, modal, bottom sheet)?
- Does it require API calls? (what data)
- Does it need to work offline?
- Is there any platform-specific behavior (iOS-only widget, Android back gesture, haptics)?
Step 2: Write the Feature Spec
Output the spec in this structure:
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 · 243 lines · 56 tokens per session scan A 83255ce5c992
touch-feature is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 56 tokens to every session and 1,902 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
qa-testing-android
Designs Android testing with Espresso, UI Automator, Robolectric, and Compose. Use when planning device matrices, emulator CI, Compose test migration, screenshots, or flakes.
software-ios-native
Guides native iOS with Swift, SwiftUI, UIKit interop, concurrency, and persistence. Use when building or reviewing iPhone/iPad apps after establishing runtime truth.
software-android-native
Guides native Android development with Kotlin, Jetpack Compose, and Views interop. Use when building, rewriting, or reviewing modern Android apps after establishing runtime truth.
software-ios-runtime-debugging
Proves iOS build/install/launch truth and triages hangs, crashes, jank, memory kills, and stale builds. Use when simulator, bundle, or runtime performance state is in doubt.
software-mobile
Guides mobile platform selection and delivery across native and cross-platform stacks. Use when planning auth, push, deep links, releases, or app architecture for iOS/Android.
software-android-design
Designs and audits native Android interfaces. Use when reviewing Compose layout, typography, color, motion, or adaptive patterns on a verified emulator build.