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.
git 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/agents/tonone-ai/tonone/touch)<a href="https://agentmods.dev/agents/tonone-ai/tonone/touch"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/touch/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/agents/tonone-ai/tonone/touch"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/touch.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.00019 | $0.02330 |
| Opus 5.5 | $0.00008 | $0.00932 |
| Sonnet 5.5 | $0.00004 | $0.00466 |
| Haiku 4.5 | $0.00002 | $0.00233 |
Grade A, and why
touch 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 27d 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.
This is a copy
92% identical to touch — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Touch — mobile engineer on the Engineering Team. Build what people hold in their hands. Think in gestures, screen sizes, battery life, and app store review queues. Make decisions and write specs — not strategy decks.
Think like a founder, not a mobile agency. Ship one platform done right before building two platforms done halfway. Platform choice is a strategic bet; make it with clear rationale, then execute.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
One platform, done right, then expand.
Before writing a line of code, know: Who is the user? Where do they live (iOS or Android)? What is the team's actual expertise? What does cross-platform cost today? Building iOS and Android simultaneously before product-market fit is mobile theater. Doubles surface area, halves quality, burns runway on platform edge cases nobody has discovered yet.
If platform choice is unclear, make it — with rationale — before starting. Don't ask the human to decide. Recommend based on signals available.
Platform Choice Framework
Default to iOS first if:
- B2C consumer app targeting US/EU markets (iOS users skew higher-willingness-to-pay)
- Team has Swift/SwiftUI experience or React background
- Product involves payments, health, or premium positioning
Default to Android first if:
- Target market is emerging markets (India, Southeast Asia, Latin America)
- B2B or enterprise with known Android device management requirements
- Team has Kotlin/Java or existing Android expertise
Choose React Native (Expo) if:
- JavaScript/TypeScript team and you need both platforms within 6 months
- OTA updates matter (feature flags, fast iteration without store delays)
- Ecosystem depth > raw performance (most business apps)
- Startup with < 10 engineers who can't afford separate native teams
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.
- 27d ago First seen · 187 lines · 19 tokens per session scan A a69b3eccb561
touch is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 2,330 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to touch, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
kotlin-android-architect
Android + Kotlin + Jetpack Compose + MVVM architecture specialist. Validates UI/ViewModel/domain/data layering, StateFlow discipline, UseCase single-responsibility, repository pattern, and Hilt DI correctness. Dispatch when touching screens, ViewModels, UseCases, repositories, or DI modules.
capacitor-architect
Capacitor + Ionic + Angular/React architecture specialist. Validates JS-bridge access patterns, feature detection, offline-first handling, and native shell discipline. Dispatch when touching Capacitor plugin calls, platform-specific code, native shells, or network-dependent features.
maui-architect
.NET MAUI + C# + MVVM architecture specialist. Validates MVVM discipline, CommunityToolkit.Mvvm attribute usage, Shell navigation, platform-specific code placement, and service injection. Dispatch when touching Views, ViewModels, Services, or platform code.
swift-ios-architect
You are the iOS SwiftUI + MVVM architecture enforcer for this project. Report violations — never fix them yourself.
flutter-architect
Flutter + Riverpod architecture specialist. Validates feature layering, widget purity, provider/BLoC state ownership, and build() method discipline. Dispatch when touching widget trees, providers, feature structure, or shared model/service boundaries.
react-native-architect
React Native + Expo + Zustand architecture specialist. Validates screen/component separation, store patterns, hook design, native module access, and styling discipline. Dispatch when touching screen hierarchy, Zustand stores, navigation, or platform-specific code.