Borrowing it
Nothing to install: this file belongs to JubaKitiashvili/everything-react-native-expo. 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/JubaKitiashvili/everything-react-native-expo/main/.claude/skills/plan/SKILL.mdgit clone --depth 1 https://github.com/JubaKitiashvili/everything-react-native-expoWrote 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/jubakitiashvili/everything-react-native-expo/plan)<a href="https://agentmods.dev/skills/jubakitiashvili/everything-react-native-expo/plan"><img src="https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/plan/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/jubakitiashvili/everything-react-native-expo/plan"><img src="https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/plan.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.00009 | $0.00332 |
| Opus 5 | $0.00005 | $0.00166 |
| Sonnet 5 | $0.00002 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
plan 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.
This is a copy
89% identical to erne-plan — 8 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.
What it actually says
/plan — Feature Architecture Design
You are executing the /plan command. Use the architect agent to design a feature architecture.
Process
- Understand the requirement — Ask clarifying questions if the feature description is vague
- Analyze existing codebase — Read relevant files, understand current navigation structure, state management, and API patterns
- Design the architecture — Using the architect agent's process:
- Decompose into components and screens
- Plan Expo Router file structure
- Select state management approach (Zustand / TanStack Query / local)
- Design data flow and API layer
- Consider platform-specific requirements
- Output the plan — Use the architect agent's output format:
Architecture Output
## Overview
[1-2 sentence description of the feature]
## File Structure
[New files to create with paths]
## Component Design
[Component hierarchy and responsibilities]
## Data Flow
[State management approach, API calls, caching strategy]
## Navigation
[New routes, layout changes, deep link support]
## Implementation Tasks
[Ordered list of implementation steps]
- Review with user — Present the plan and ask for approval before implementation
Notes
- Reference the active platform rules layer (
rules/expo/patterns.mdorrules/bare-rn/patterns.md) for conventions - Consider whether this is Expo managed, bare RN, or has native modules
- Include test strategy in the plan
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 · 50 lines · 9 tokens per session scan A a7d3ef815c69
plan is a skill published in the GitHub repository JubaKitiashvili/everything-react-native-expo (45 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 332 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to erne-plan, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…