Borrowing it
Nothing to install: this file belongs to MannanSaood/termi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MannanSaood/termi/main/.cursor/skills/add-keyboard-toolbar-gesture/SKILL.mdgit clone --depth 1 https://github.com/MannanSaood/termiWrote 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/mannansaood/termi/add-keyboard-toolbar-gesture)<a href="https://agentmods.dev/skills/mannansaood/termi/add-keyboard-toolbar-gesture"><img src="https://agentmods.dev/badge/skills/mannansaood/termi/add-keyboard-toolbar-gesture/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/mannansaood/termi/add-keyboard-toolbar-gesture"><img src="https://agentmods.dev/badge/skills/mannansaood/termi/add-keyboard-toolbar-gesture.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.00038 | $0.00862 |
| Opus 5 | $0.00019 | $0.00431 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
add-keyboard-toolbar-gesture 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 10d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is the Phase 1c "cheapest, highest-visibility win" item — pure
Compose UI, no Rust changes needed. CommandToolbar.kt already has
Esc/Home/End buttons and the basic Ctrl+C/D/Z/Tab/arrow buttons; this
skill covers the two remaining pieces.
1. Sticky-Ctrl modifier
Goal: tap "Ctrl" once, it visually arms, the next character typed sends that character's control code instead of the literal character, then it disarms automatically.
// In TerminalScreen.kt (or wherever CommandToolbar is hosted) —
// this state needs to live above the toolbar since it also affects how
// regular keyboard input is interpreted, not just toolbar buttons:
var ctrlArmed by remember { mutableStateOf(false) }
// Toolbar button:
ToolbarButton(
text = "Ctrl",
// Use a different visual state when armed — e.g. filled vs outlined —
// so the user has clear feedback the modifier is "waiting."
onClick = { ctrlArmed = !ctrlArmed }
)
// Wherever regular character input is sent to the PTY (likely in
// TerminalViewModel or the text input handler in TerminalView.kt):
fun sendChar(c: Char) {
if (ctrlArmed) {
val controlCode = (c.uppercaseChar().code - 'A'.code + 1)
if (controlCode in 1..26) {
onCommand(controlCode.toChar().toString())
}
ctrlArmed = false // disarm after one use
} else {
onCommand(c.toString())
}
}
Check TerminalViewModel.kt and TerminalView.kt for where character
input actually currently gets sent to the PTY before wiring this in — the
sketch above assumes a single sendChar/onCommand chokepoint, which may
need confirming against the actual current implementation.
2. Swipe-based history cycling
Goal: swipe left/right on the toolbar area to cycle command history, as an alternative to repeatedly tapping ↑/↓.
import androidx.compose.foundation.gestures.detectHorizontalDragGestures
import androidx.compose.ui.input.pointer.pointerInput
Row(
modifier = modifier
.fillMaxWidth()
.pointerInput(Unit) {
detectHorizontalDragGestures { change, dragAmount ->
change.consume()
if (dragAmount > 20) onArrowUp() // swipe right → older
else if (dragAmount < -20) onArrowDown() // swipe left → newer
}
}
// ...existing modifiers (background, horizontalScroll, padding)
) { /* existing buttons */ }
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.
- 10d ago First seen · 96 lines · 38 tokens per session scan A d04417865404
add-keyboard-toolbar-gesture is a skill published in the GitHub repository MannanSaood/termi (8 stars, last pushed 10d ago), licensed MIT. It adds 38 tokens to every session and 862 once invoked, about $0.0002 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-31.
Other skills, from other repositories
sceneview-ios
Build 3D and AR apps on Apple platforms (iOS, macOS, visionOS) with SceneViewSwift — the SwiftUI wrapper around RealityKit. Use whenever the user asks for "3D in SwiftUI", "AR with ARKit in SwiftUI", a model viewer for iOS, or any Apple-platform 3D/AR app where the dependency is the SceneViewSwift Swift Package from…
sceneview
Build 3D and AR apps with the SceneView SDK in Jetpack Compose, SwiftUI (iOS/macOS/visionOS via SceneViewSwift), Web (Filament.js), Flutter and React Native. Use whenever the user asks for "3D in Compose", "AR with ARCore in Compose", a model viewer, or any cross-platform 3D/AR app where the dependency is…
compose-animations
Use when writing or reviewing Jetpack Compose motion: visibility enter/exit, animating one property toward a target, color or size transitions, multiple properties from one state, switching composable content, or choosing between AnimatedVisibility, animateAsState, rememberTransition, AnimatedContent, and Crossfade.
compose-focus-navigation
Use when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus behavior.
compose-state-and-effects
Use when writing or reviewing Jetpack Compose state ownership, remember state, state hoisting, screen state holders, LaunchedEffect, DisposableEffect, SideEffect, Flow collection, navigation, snackbar, analytics, or focus requests.
compose-component-design
Use when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout placement, caller-provided variable content, primitive content parameters, optional content, or boolean shape flags.