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/jni-safety-review/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/jni-safety-review)<a href="https://agentmods.dev/skills/mannansaood/termi/jni-safety-review"><img src="https://agentmods.dev/badge/skills/mannansaood/termi/jni-safety-review/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/jni-safety-review"><img src="https://agentmods.dev/badge/skills/mannansaood/termi/jni-safety-review.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.00051 | $0.00802 |
| Opus 5 | $0.00026 | $0.00401 |
| Sonnet 5 | $0.00010 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
jni-safety-review 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 11d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this before merging any change that touches android_jni.rs,
jni_safe.rs, or vfs/android_saf.rs — this is the highest-consequence
code in the repo, since a mistake here crashes the whole app instead of
returning an error.
Checklist
- No raw
JNIEnvmethod calls outsidejni_safe.rs's wrappers. If you wroteenv.call_method(...)directly anywhere else, stop and usejni_safe::safe_call_*_methodinstead. - Every JNI call is followed by exception checking
(
jni_safe::check_and_clear_exception), not left to propagate as an unchecked pending exception. - No
.unwrap()/.expect()anywhere in the call chain from a JNI entry point (extern "C" fn Java_...) down through whatever it calls. A panic that unwinds across the FFI boundary is undefined behavior in Rust — it must never happen. Usecatch_unwindat the JNI entry point if there's any doubt (checkandroid_jni.rsfor the existing pattern before adding a new export). - Handles crossing the boundary go through
jni_safe::handle_box/handle_to_ptr/handle_to_ref/handle_to_mut/handle_drop— never a raw pointer cast. Handles are opaque positive IDs, notBox::into_raw as i64. Kotlin must not usehandle > 0as the only check if an old .so might still return tagged pointers; error codes are only-1..-99. SeeErrorCode.isValidHandle. - New JNI-crate-dependent code (anything using
JNIEnv,JObject,JString, etc.) is behind#[cfg(feature = "android")]. Verify with:bash cd rust && cargo check --features android --all-targets cd rust && cargo check --target aarch64-linux-android --features android --lib cd rust && cargo build --no-default-features # must NOT need the jni crateIfcargo build --no-default-featuresfails because it's pulling injni, something new isn't properly feature-gated. - If this touches
vfs/android_saf.rs: does the change respect the capability system?SafProvidershould NOT implementchmod/symlink— if you're adding code there that makes those "work" via some workaround, that's very likely wrong; SAF genuinely doesn't support these, and pretending otherwise will produce confusing partial failures for users. Talk to whoever owns this repo before doing this.
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.
- 11d ago First seen · 64 lines · 51 tokens per session scan A 83811e628d78
jni-safety-review is a skill published in the GitHub repository MannanSaood/termi (8 stars, last pushed 11d ago), licensed MIT. It adds 51 tokens to every session and 802 once invoked, about $0.0003 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.