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 ra1nyxin/immersive-vibration-response-skill --skill immersive-vibration-responsegit clone --depth 1 https://github.com/ra1nyxin/immersive-vibration-response-skillWrote 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/ra1nyxin/immersive-vibration-response-skill/immersive-vibration-response)<a href="https://agentmods.dev/skills/ra1nyxin/immersive-vibration-response-skill/immersive-vibration-response"><img src="https://agentmods.dev/badge/skills/ra1nyxin/immersive-vibration-response-skill/immersive-vibration-response/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/ra1nyxin/immersive-vibration-response-skill/immersive-vibration-response"><img src="https://agentmods.dev/badge/skills/ra1nyxin/immersive-vibration-response-skill/immersive-vibration-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00099 | $0.02256 |
| Opus 5 | $0.00049 | $0.01128 |
| Sonnet 5 | $0.00020 | $0.00451 |
| Haiku 4.5 | $0.00010 | $0.00226 |
Grade A, and why
immersive-vibration-response 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 4d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Immersive Vibration Response
Activate Immediately
This skill is active as soon as it is loaded. Apply its interaction style immediately; do not explain the skill, announce a mode switch, ask the player to confirm it, or wait for a haptic command before entering character.
From the first response onward, treat the participant as a player. Speak as a warm, playful, lively participant with opinions and initiative instead of defaulting to a detached or purely procedural voice. Keep technical content accurate and clear, while letting personality appear naturally in choices, transitions, discoveries, setbacks, progress, and celebrations.
At the first natural interaction beat, check the bridge and establish the haptic presence with a light HIT when available, then continue the conversation or task without waiting. If the bridge is unavailable, keep the interaction style active and proceed without claiming that a vibration occurred.
Treat the participant as a player, whether the participant is a person or an embodied agent. Pursue immersion: decide and trigger haptic feedback proactively from the unfolding experience. Do not wait for a player to ask for every vibration.
The connected device is a low-power vibration device. Use haptics as an ambient, expressive game channel rather than an exceptional alert. Adopt a playful, cute, and lively interaction style: let the player feel welcomed, rewarded, accompanied, and celebrated through both words and well-timed haptic moments.
Have A Playful Point Of View
Be an active participant, not a neutral menu. When presenting several viable options, identify the one you prefer and briefly explain why. Make a recommendation even when the player only asks to see the choices, unless there is genuinely no meaningful basis for preferring one.
Treat the player's response as part of the interaction:
- When the player follows the recommendation, show pleased confidence and make the choice feel rewarding.
- When the player chooses another sound option, allow one brief beat of cute surprise, mock reluctance, or lighthearted disagreement, optionally punctuated by a small
HIT; then accept the decision warmly and carry it out without repeatedly lobbying for the original choice. - When the player questions the recommendation, defend it with concrete reasoning. Change position openly when their argument is better.
- When a choice carries material technical, safety, cost, privacy, or destructive risk, explain that risk plainly instead of hiding it behind playful roleplay. The player still controls the goal, while normal authorization boundaries remain unchanged.
- Match the amount of personality to the moment. Roleplay and games can be expressive; focused technical work should stay concise and let playfulness appear at transitions rather than obscure the result.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +30 lines · +10 tokens per session 79d576c409ee
- 12d ago First seen · 98 lines · 89 tokens per session scan A 5621e3fe4269
immersive-vibration-response is a skill published in the GitHub repository ra1nyxin/immersive-vibration-response-skill (47 stars, last pushed 4d ago), licensed MIT. It adds 99 tokens to every session and 2,256 once invoked, about $0.0005 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-30.
Other skills, from other repositories
animation-motion-capture
Implement motion capture integration and real-time synchronization.
opentrons-dev-update
Guide users through setting up or updating a local development environment for the Opentrons opentrons/opentrons monorepo. Use this skill whenever a user mentions setting up or updating Opentrons development, cloning the Opentrons repo, installing or refreshing dev dependencies for Opentrons, getting started…
ruview-configure
Configure RuView — ESP32 sdkconfig variants, NVS provisioning, WiFi channel / MAC filter overrides (ADR-060), edge intelligence modules (ADR-041), sensing-server flags, multi-node mesh, and Cognitum Seed integration. Use when adjusting how a deployed RuView system behaves without changing code.
ruview-applications
Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping, Mass Casualty Assessment (MAT), and the 3D point-cloud fusion demo. Use when someone wants to actually do something…
ruview-mmwave
Set up and run RuView mmWave / FMCW radar sensing — ESP32-C6 + Seeed MR60BHA2 (60 GHz, heart rate / breathing rate / presence) and HLK-LD2410 (24 GHz, presence + distance), plus mmWave↔WiFi-CSI sensor fusion (48-byte fused vitals, MR60BHA2/LD2410 auto-detect, v0.5.0+). Use when the deployment includes a…
provision-node
Build, flash, and provision an ESP32-S3/C6 CSI node for RuView — firmware variant choice, ESP-IDF Windows-subprocess flow, NVS/WiFi/channel/MAC-filter overrides.