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 skills/lykhoyda/rn-dev-agent/rn-workflownpx skills add Lykhoyda/rn-dev-agent --skill rn-workflowgit clone --depth 1 https://github.com/Lykhoyda/rn-dev-agentWhat 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 | $0.00141 | $0.03242 |
| Opus 5 | $0.00071 | $0.01621 |
| Sonnet 5 | $0.00028 | $0.00648 |
| Haiku 4.5 | $0.00014 | $0.00324 |
Grade A, and why
rn-workflow 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 2d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rn-workflow — the proven operating sequence, in order
This skill owns the sequencing of a real React Native journey. The
authoritative content stays where it lives today: check-env owns inventory,
setup owns onboarding, capturing-proof owns evidence gates, and the
rn_session tool owns every refusal. Execute the steps below in order; never
reorder, skip, or re-derive them from memory.
Each step is: one action → one authoritative readback → one bounded stop.
There is no internal state to track — the only state ever consulted is a fresh
rn_session(action="status") projection.
When to use
- Before any journey that will touch a simulator/emulator (build, test, proof).
- When asked to "get the app ready", "validate the setup", or after repeated session/device failures.
When NOT to use
- Pure code reading or editing with no device work — no session is needed.
- Plugin installation diagnostics — that is
/rn-dev-agent:doctor. - Project onboarding — that is
/rn-dev-agent:setup(Step 0 stops and routes there if onboarding is missing).
The contract
0 read instructions ─► 1 pkg-manager + deps ─► 2 read-only inventory
│
2a classify ownership (status only)
▼
3 one exact device ─► 4 integration + managed Metro ─► 5 bind + requested proof
│
6 truthful evidence ─► 7 reverse cleanup + postflight
Step 0 — Read the authoritative local instructions
Read the project's injected CLAUDE.md block (from
## React Native Development (rn-dev-agent) through
<!-- rn-dev-agent:template-end -->) and .rn-agent/local/troubleshooting.md.
If the block is absent → stop: "project not onboarded — run
/rn-dev-agent:setup". Never start device work on an un-onboarded project.
Step 1 — Package manager and dependencies
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.
- 2d ago First seen · 257 lines · 141 tokens per session scan A 069cf7228b97
rn-workflow is a skill published in the GitHub repository Lykhoyda/rn-dev-agent (11 stars, last pushed 3d ago), licensed MIT. It adds 141 tokens to every session and 3,242 once invoked, about $0.0007 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
skill-packager
Authors Agent Skills v1.0 packages (SKILL.md plus references/scripts), runs packageskill to produce a standards-compliant zip, and uses installskill to add skills from HTTPS, registry, workspace, or an uploaded archive. Use when the user wants to turn documentation, workflows, or code into a portable skill, export a…
document-processor
Guidance for processing documents, extracting content, and transforming structured information. Use when the user asks to process, parse, extract, or transform document content such as PDFs, Word files, or spreadsheets.
workflow-helper
Guidance for creating, managing and executing workflow automations that chain multiple tools and agents together. Use when the user asks about building, listing, running or composing workflows and automated task pipelines.
attendance-signin-sheet
Generate printable attendance / 签到表 spreadsheets from name lists. Use when the user asks for 签到表, attendance sheet, meeting sign-in table, or similar printable roster tables (not full payroll attendance scoring unless asked).
data-analyzer
Guidance for analyzing structured data, generating statistics and producing data-driven insights. Use when the user asks to analyze data, compute statistics, find patterns, or generate analytical reports.
procurement-audit
Review procurement contracts and purchase packages against uploaded compliance rules (招标/采购制度). Use for 采购审核, contract compliance checklists, or procurement statistics rollups.