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 test-featuregit 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/test-feature)<a href="https://agentmods.dev/skills/lykhoyda/rn-dev-agent/test-feature"><img src="https://agentmods.dev/badge/skills/lykhoyda/rn-dev-agent/test-feature/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/test-feature"><img src="https://agentmods.dev/badge/skills/lykhoyda/rn-dev-agent/test-feature.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.00038 | $0.00248 |
| Opus 5.5 | $0.00015 | $0.00099 |
| Sonnet 5.5 | $0.00008 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
test-feature 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 1mo 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
72% identical to build-and-test — 10 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
test-feature
Invoke this workflow explicitly as $rn-dev-agent:test-feature [request text].
The exact text after the skill mention is the conceptual request. It is user-message data, not a shell variable or a Claude command-template substitution. Preserve it while applying the workflow's documented grammar; pass only separately parsed and validated values to MCP tools or package helpers. Never use eval or interpolate the raw request into a shell command.
Read the complete package-local workflow before acting. Resolve that file and every helper relative to this exact SKILL.md path; never scan Codex caches or rely on a plugin-root environment variable. If a required cdp MCP tool is absent from the active task, stop and use the read-only discovery diagnosis. Do not substitute raw Maestro for rn-dev-agent strict proof.
What ships with it
1 file 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.
- 1mo ago Changed d29b1169d955
- 1mo ago First seen · 14 lines · 38 tokens per session scan A a748635cd744
test-feature is a skill published in the GitHub repository Lykhoyda/rn-dev-agent (20 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 248 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 72% identical to build-and-test, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
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.
pod-e2e
ONLY for developing Kiro Crew itself -- if the project you are working on is anything else, ignore this skill: it drives Kiro Crew's own pod tooling, which does not exist in another repository. Boots a Kiro Crew feature worktree's full stack as an ISOLATED throwaway pod and proves it boots, authenticates and renders…
android-emulator
Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an Android virtual device.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
nexent-daily-test
A procedure for running Nexent daily, full-layer tests on a self-hosted Ubuntu machine. Nexent is tested across separate layers such as unit, service, AI runtime, and browser journeys, with results and evidence kept locally.
tfp-verification
Generate a deterministic report for disposable executor acceptance tests.