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 tjdrhs90/rn-launch-harness --skill rn-harness-admobgit clone --depth 1 https://github.com/tjdrhs90/rn-launch-harnessWrote 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/tjdrhs90/rn-launch-harness/rn-harness-admob)<a href="https://agentmods.dev/skills/tjdrhs90/rn-launch-harness/rn-harness-admob"><img src="https://agentmods.dev/badge/skills/tjdrhs90/rn-launch-harness/rn-harness-admob/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/tjdrhs90/rn-launch-harness/rn-harness-admob"><img src="https://agentmods.dev/badge/skills/tjdrhs90/rn-launch-harness/rn-harness-admob.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 204 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 211 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 603 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 211 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.
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.00027 | $0.05276 |
| Opus 5 | $0.00014 | $0.02638 |
| Sonnet 5 | $0.00005 | $0.01055 |
| Haiku 4.5 | $0.00003 | $0.00528 |
Grade A, and why
rn-harness-admob 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 7d 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 — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rn-harness-admob — Phase 7: AdMob Integration
Integrate AdMob ads into the app. Analyze the app to determine the best ad strategy, then guide the user through manual ad unit creation and inject code automatically.
Trigger
Called by the orchestrator as Phase 7.
Input
docs/harness/plans/YYYY-MM-DD-prd.md(PRD with ad placement strategy)docs/harness/config.md(AdMob settings)- Actual project code (screens, navigation structure)
Process
Step 0: Skip Check
If config.md has admob.enabled: false → skip this phase entirely.
Step 1: Analyze App for Ad Strategy
Read the actual project code to understand:
- Screen count and types: How many screens? Which are content-heavy vs action-heavy?
- User flow: What are the main navigation paths?
- Content type: List-based? Tool/utility? Media? Social?
- Session pattern: Quick in-and-out? Or long sessions?
Based on analysis, determine the optimal ad mix:
Banner Ads — DEFAULT: ALL SCREENS (unless excluded)
Banners go on every screen except where they harm UX:
Include (banner on):
- Home / main feed
- List screens
- Detail / content screens
- Profile / settings
- Search / explore
- Any screen where user spends time reading/browsing
Exclude (no banner):
- Login / signup / onboarding (first impression matters)
- Full-screen media playback (video, camera)
- Payment / checkout flow
- Modal dialogs
- Screens with keyboard-heavy input (forms with many fields)
Banner placement: Bottom of SafeAreaView, above tab bar (if tabs exist) or at screen bottom.
Interstitial Ads — Context-Aware Placement
Analyze navigation patterns and place interstitials at natural transition points:
| App Type | Best Interstitial Triggers |
|---|---|
| Content/News | After reading 3+ articles, on back navigation from detail |
| Utility/Tool | After completing a task (save, export, convert) |
| List/Directory | After viewing 5+ detail pages in a session |
| Game | Between levels, after game over |
| Social | NOT recommended (disrupts social flow) |
| E-commerce | After adding to cart (NOT during checkout) |
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.
- 7d ago Changed · +36 lines c043488f009d
- 11d ago First seen · 581 lines · 27 tokens per session scan A fbc36c29eede
rn-harness-admob is a skill published in the GitHub repository tjdrhs90/rn-launch-harness (9 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 5,276 once invoked, about $0.0001 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-31.
Other skills, from other repositories
appstore-publish
A workflow guide for publishing an app to the App Store, including prerequisites, tool loading, submission, and resubmission steps.
playstore-publish
A guide for publishing to Google Play, including required conditions, tool loading, the run sequence, in-app products, and subscriptions. Google Play is Google’s store for Android apps and digital purchases.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
ios-marketing-capture
Use when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances. Covers full-screen shots, isolated element renders (carousel cards, widgets), and reproducible output naming. Triggers on marketing screenshots, locale screenshots, widget…
implementation-guide
Generates detailed implementation guide with pseudo-code and step-by-step development instructions. Creates IMPLEMENTATIONGUIDE.md from PRD, Architecture, and UX specs. Use when creating development roadmap.
architecture-spec
Generates technical architecture specification from PRD. Covers architecture pattern, tech stack, data models, and app structure. Use when creating ARCHITECTURE.md or designing system architecture.