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 agentmods add instructions/levifig/rails-instructions/rails-mobilegit clone --depth 1 https://github.com/levifig/rails-instructionsWrote 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/instructions/levifig/rails-instructions/rails-mobile)<a href="https://agentmods.dev/instructions/levifig/rails-instructions/rails-mobile"><img src="https://agentmods.dev/badge/instructions/levifig/rails-instructions/rails-mobile.svg" alt="Measured on agentmods" 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.00960 | $0.00960 |
| Opus 5 | $0.00480 | $0.00480 |
| Sonnet 5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
rails-instructions rails-mobile.instructions.md 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 5d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotwire Native Guidelines
Core Concepts
- Hotwire Native displays web content in a native shell with platform-specific navigation
- Web content renders in a WebView with native-feeling transitions and behaviors
- Link navigation is intercepted and handled by the native adapter
- Build once for the web, deploy simultaneously to web and native mobile apps
- Progressively enhance with native components where higher fidelity is needed
Navigation Best Practices
- Design web content to work across web, iOS, and Android
- Links between pages become native screen transitions automatically
- External links open in an in-app browser (SFSafariViewController on iOS, Custom Tabs on Android)
- Use
data-turbo-action="replace"to replace the current screen instead of pushing a new one - Ensure all screens are accessible via URLs for proper native navigation
Path Configuration
- Define platform-specific navigation rules in a JSON configuration file
- Host configuration files at versioned URLs (e.g.,
/configurations/ios_v1.json) - Include both local (bundled) and remote (server-hosted) configurations
- Use regex patterns to match URLs and apply specific behaviors
- Configuration example:
{
"settings": {
"feature_flags": [
{
"name": "enable_new_feature",
"enabled": true
}
]
},
"rules": [
{
"patterns": ["/modal/.*"],
"properties": {
"context": "modal"
}
},
{
"patterns": ["/tabs/.*"],
"properties": {
"presentation": "refresh"
}
}
]
}
Bridge Components
- Use Bridge Components for web-to-native communication
- Components have both web (Stimulus) and native (Swift/Kotlin) counterparts
- Register component handlers in your native app and attach web controllers in HTML
- Use for native UI elements like top bar buttons, action sheets, and platform APIs
- Web component implementation example:
// app/javascript/controllers/native_button_controller.js
import { Controller } from "@hotwired/stimulus";
import { BridgeComponent } from "@hotwired/bridge";
export default class extends Controller {
static values = { title: String, style: String };
connect() {
this.bridge = new BridgeComponent("button", this);
this.bridge.send("connect", {
title: this.titleValue,
style: this.styleValue || "default",
});
}
disconnect() {
this.bridge.send("disconnect");
}
handleTap(message) {
// Handle tap event from native
const form = this.element.closest("form");
if (form) form.requestSubmit();
}
}
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.
- 5d ago First seen · 144 lines · 960 tokens per session scan A 90075f958ed9
rails-instructions rails-mobile.instructions.md is an instructions file published in the GitHub repository levifig/rails-instructions (54 stars, last pushed 1y ago), licensed MIT. It adds 960 tokens to every session, about $0.0048 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 instructions, from other repositories
mcp-android-server-python copilot-instructions.md
Instructions for nim444/mcp-android-server-python, covering mcp android agent and available mcp tools.
claude-code-settings copilot-instructions.md
Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.
agent-rules testing.instructions.md
Instructions for lirantal/agent-rules, covering testing guidelines for node.js applications, general testing principles, guiding principles, descriptive test naming (three-part structure) and structure tests by the aaa pattern.
debroid AGENTS.md
Instructions for PatilShreyas/debroid, covering ai agent contributor guide 🤖, 🎯 intention & motivation, 🏗️ architecture & layers, 1. the core layer (jdi & adb orchestration) and 2. the cli layer (daemon & client).
apex-accelerator code-quality.instructions.md
Code quality guidelines: commenting best practices (WHY not WHAT) and review priorities with security checks.
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.