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 droid-ash/finalrun-agent --skill finalrun-use-cligit clone --depth 1 https://github.com/droid-ash/finalrun-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/droid-ash/finalrun-agent/finalrun-use-cli)<a href="https://agentmods.dev/skills/droid-ash/finalrun-agent/finalrun-use-cli"><img src="https://agentmods.dev/badge/skills/droid-ash/finalrun-agent/finalrun-use-cli/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/droid-ash/finalrun-agent/finalrun-use-cli"><img src="https://agentmods.dev/badge/skills/droid-ash/finalrun-agent/finalrun-use-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 40 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 96 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 265 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 125 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00055 | $0.03038 |
| Opus 5.5 | $0.00022 | $0.01215 |
| Sonnet 5.5 | $0.00011 | $0.00608 |
| Haiku 4.5 | $0.00006 | $0.00304 |
Grade A, and why
finalrun-use-cli 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.
How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinalRun CLI Guide and Operator
You help repo users safely use the published finalrun CLI inside repositories that contain .finalrun/. Default to published CLI usage in app repositories, not monorepo contributor workflows, unless the user explicitly asks for contributor setup.
Prerequisites
Install the published package and confirm the CLI is available:
npm install -g @finalrun/finalrun-agent
finalrun --help
For local Android or iOS execution, use finalrun doctor as the first host-readiness diagnostic.
finalrun doctor
Source of Truth
- Prefer local CLI help such as
finalrun --help,finalrun test --help, andfinalrun suite --help. - Inspect the actual workspace files under
.finalrun/before giving execution advice. - Check
.finalrun/config.yaml,.finalrun/env/,.finalrun/tests/, and.finalrun/suites/before asking questions that the repo can answer. - Do not invent unsupported commands such as
finalrun init.
Core Workflow
- Inspect the workspace and confirm
finalrunis available onPATHwhen command execution matters. - Validate first with
finalrun checkso selectors, suites, config, env bindings, and app overrides are verified before the user relies on a run result. - Explain the exact
finalrun testorfinalrun suitecommand you intend to use, including the selected--env,--platform, and--modelwhen relevant. - Treat validation failures as blockers. Explain the CLI error in plain language and do not pretend the test run happened.
- Use
finalrun runsto inspect recent run artifacts after validation or execution. - Ask before starting
finalrun start-server, because those commands launch background UI behavior. - If the user wants to create or edit YAML tests, suites, or env bindings, route that work to
finalrun-generate-test.
Missing Workspace
If .finalrun/ is missing:
- explain that FinalRun must run from a repository containing
.finalrun/ - clarify that only
.finalrun/testsis always required;suites/is only required for suite-based workflows - show the expected structure
- offer a scaffold plan or route the user to
finalrun-generate-test - do not claim that the CLI can bootstrap the workspace automatically
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 First seen · 301 lines · 55 tokens per session scan A 7e47c9b96f0f
finalrun-use-cli is a skill published in the GitHub repository droid-ash/finalrun-agent (311 stars, last pushed 4d ago), licensed Apache-2.0. It adds 55 tokens to every session and 3,038 once invoked, about $0.0002 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
playwright-for-android
End-to-end Android debug loop on an emulator. Builds the APK with a Gradle task, boots a named AVD, installs and launches the target package, then drives a single feature via adb-injected UI actions while capturing a unified logcat-and-actions timeline plus a developer-facing test report. Use when the user wants to…
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
argent-create-flow
Create, record, edit, replay, or repair reusable Argent flow YAML files. Use when the user asks to record or replay a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-flows. Also use before repeating three or more interactions. For one-off UI checks…