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.
/plugin marketplace add rahulkeerthi/expo-toolkitnpx agentmods add plugins/rahulkeerthi/expo-toolkit/marketplacegit clone --depth 1 https://github.com/rahulkeerthi/expo-toolkitWrote 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/plugins/rahulkeerthi/expo-toolkit/marketplace)<a href="https://agentmods.dev/plugins/rahulkeerthi/expo-toolkit/marketplace"><img src="https://agentmods.dev/badge/plugins/rahulkeerthi/expo-toolkit/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
withqwerty marketplace 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 6d 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.
What it actually says
{
"name": "withqwerty",
"owner": {
"name": "Rahul Keerthi",
"email": "[email protected]"
},
"metadata": {
"description": "Mobile development tools for Claude Code",
"version": "1.1.0",
"homepage": "https://github.com/rahulkeerthi/expo-toolkit",
"license": "MIT"
},
"plugins": [
{
"name": "expo-toolkit",
"source": {
"source": "github",
"repo": "rahulkeerthi/expo-toolkit"
},
"description": "Expo app development - init, builds, submissions, updates",
"version": "0.1.0",
"author": {
"name": "Rahul Keerthi + Claude"
},
"keywords": ["expo", "react-native", "eas", "mobile"]
},
{
"name": "appstore-connect-mcp",
"source": {
"source": "github",
"repo": "rahulkeerthi/appstore-connect-mcp"
},
"description": "App Store Connect API - metadata, builds, TestFlight, IAP",
"version": "0.1.0",
"author": {
"name": "Rahul Keerthi + Claude"
},
"keywords": ["app-store", "ios", "testflight", "iap"]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 6d ago First seen · 42 lines scan A ef7949441965
withqwerty marketplace is a plugin published in the GitHub repository rahulkeerthi/expo-toolkit (5 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ios
iOS plugin.
mobile-development
Build, test, sign, and ship mobile apps across iOS, Android, Flutter, and React Native — project scaffolding, builds and code signing, device and emulator testing, store submission (App Store and Play Store), app lifecycle and backgrounding, offline and sync, and mobile-specific testing. Use when the task involves…
atlas-publish
Takes the open PRs of the Atlas/Bella monorepo to a registered draft release on either the over-the-air or the App Store lane, classifying between them from the expo-updates native fingerprint rather than from intent — ios.buildNumber sits inside that fingerprint, so a buildNumber bump alone forces a store release.…
safe-android-reverser
Sandboxed Android reverse engineering with semantic program indexing, XREF/CFG queries and structured network evidence through MCP.
eternal-pose
Build and evolve map-first, mobile-first travel sites from real itinerary material.
swift-performance-pro
Performance: Instruments, SwiftUI render cost, memory and retain cycles, launch time, lists.