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 Lykhoyda/rn-dev-agent --skill creating-actionsgit clone --depth 1 https://github.com/Lykhoyda/rn-dev-agentWrote 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/lykhoyda/rn-dev-agent/creating-actions)<a href="https://agentmods.dev/skills/lykhoyda/rn-dev-agent/creating-actions"><img src="https://agentmods.dev/badge/skills/lykhoyda/rn-dev-agent/creating-actions/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/lykhoyda/rn-dev-agent/creating-actions"><img src="https://agentmods.dev/badge/skills/lykhoyda/rn-dev-agent/creating-actions.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.00127 | $0.03968 |
| Opus 5.5 | $0.00051 | $0.01587 |
| Sonnet 5.5 | $0.00025 | $0.00794 |
| Haiku 4.5 | $0.00013 | $0.00397 |
Grade A, and why
creating-actions 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 22d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
creating-actions — Author a Reusable Maestro Action
An action is a parameterised Maestro flow at <project>/.rn-agent/actions/<id>.yaml with an M7 metadata header, replayable via $rn-dev-agent:run-action or cdp_run_action (auto-repair-aware). A well-authored action turns a ~minutes interactive walk into a ~seconds deterministic replay. Authoring one well means: dedup first, ground every selector in evidence, design the flow as an ASCII diagram before writing YAML, validate, then replay to promote.
When to Use
- A verified flow is worth replaying: login, navigation prologue, multi-step setup, locale/theme switching, data seeding.
$rn-dev-agent:test-featureverification passed and the walk should be persisted.- The user asks to make a flow replayable / save an action.
When NOT to author an action:
- A one-off check — use
maestro_runwithinlineYamland throw it away. - An existing action already covers the flow — extend or parameterise it instead of forking a near-duplicate.
- The flow spans two apps — actions are single-
appIdby contract.
Step 0 — Scan the Inventory First (dedup)
Before authoring anything, check what already exists:
Resolve <package-root> from this exact skill's SKILL.md path (../.. from
the skill directory), then invoke the selected package by separately quoted
argv. Never scan caches or use a launcher-only environment variable:
node <package-root>/rn-dev-agent-core/dist/learned-actions.js --json --section b \
--workspace-root <workspace> --memory-cwd <workspace> --filter <one keyword value>
(or $rn-dev-agent:list-learned-actions <keyword>). Listing is read-only and grants no replay authority: if a match covers the goal, run the Step 6 ownership pre-flight first — call rn_session({action: "status"}), and if state is blocked, stop and follow recoveryRequirement.nextAction verbatim instead of replaying. Only then replay the match. If a near-match exists (same flow, hardcoded values), parameterise THAT action with ${VAR} placeholders rather than creating a sibling — duplicate actions rot independently and split the repair history.
What ships with it
2 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.
- 22d ago Changed 66d028989338
- 1mo ago Changed · +4 lines 0ac79beeb091
- 1mo ago Changed 305e99f2b327
- 1mo ago Changed · +2 lines 50e8e6b59a20
- 1mo ago Changed · +1 lines 07adf56e8f95
- 1mo ago First seen · 218 lines · 127 tokens per session scan A ae277b1abd1b
creating-actions is a skill published in the GitHub repository Lykhoyda/rn-dev-agent (20 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 3,968 once invoked, about $0.0005 per session on Opus 5.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
browser
Browser automation via the agent-browser CLI. Use when the user needs to drive websites or Electron apps — navigating, forms, clicks, screenshots, data extraction, testing web apps, UI checks, the dashboard Electron shell, or the user's own logged-in Chrome via the browser relay or Panerelay (SSO/2FA). Triggers: "open…
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
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.
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…
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
A spreadsheet generator for printable attendance or meeting sign-in sheets. It turns a list of names into rows with columns such as signatures, dates, departments, or employee IDs.