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 hoainho/podium-mcp --skill e2egit clone --depth 1 https://github.com/hoainho/podium-mcpWrote 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/hoainho/podium-mcp/e2e)<a href="https://agentmods.dev/skills/hoainho/podium-mcp/e2e"><img src="https://agentmods.dev/badge/skills/hoainho/podium-mcp/e2e.svg" alt="Measured on agentmods" 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.00041 | $0.00284 |
| Opus 5 | $0.00020 | $0.00142 |
| Sonnet 5 | $0.00008 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
e2e 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.
What it actually says
Parse $ARGUMENTS as:
- token 1 → UDID
- token 2 → BUNDLE_ID
- remaining text → either a file path (ends in .yaml/.yml) or a plain-language description of the journey to author
If a file path was given:
Call run_flow with udid and files: [<path>]. Report every step's pass/fail. If any step fails, quote the relevant raw output lines.
If a description was given (or nothing):
- Call
inspect_screenon the UDID to enumerate tappable elements and their exact text/ids. - Author an inline Maestro YAML that only uses selectors you actually observed — never invent text. The flow must start with
appId: <BUNDLE_ID>andlaunchApp: {stopApp: false}. - Call
run_flowwith the inlineyaml. - Report each step result. If it fails, revise the flow once using the error and re-run.
Always show the per-step steps array in your response, not just a top-level pass/fail.
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 First seen · 20 lines · 41 tokens per session scan A aaaf86484070
e2e is a skill published in the GitHub repository hoainho/podium-mcp (4 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 284 once invoked, about $0.0002 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
ios-simulator-interaction
Interaction with the iOS simulator using iosef, a CLI optimized for agent usage. Use when building or testing changes on the iOS Simulator — viewing the screen, tapping buttons, reading accessibility trees, finding elements by selector, asserting UI state, scripting multi-step test flows, installing and launching…
testa
Autonomously E2E-test iOS apps in the Simulator — read the screen (accessibility tree OR on-device OCR), tap/type/swipe/drag-drop/pinch/rotate, manage apps, and assert results. Use when asked to test, QA, drive, or reproduce a flow in an iOS app/simulator (React Native, Expo, native SwiftUI, or any app).…
xcforge
Complete reference for xcforge — 109 MCP tools + 113 CLI commands for iOS development. Covers build, test, simulator, physical devices, SPM, UI automation, screenshots, logs, git, visual regression, accessibility, localization, session profiles, diagnosis workflows, plan execution, LLDB debugger integration, bless…
scrcpy-mcp
Professional Android automation agent for device interaction, UI testing, and app management. Use for: (1) interacting with Android apps, (2) filling inputs, (3) structural UI inspection via XML/axtree, (4) complex multi-step mobile tasks. Prefer XML/axtree over screenshots — images are expensive tokens.
ios-dev
You are an expert iOS developer with full autonomous control of the Xcode build pipeline, iOS Simulator, screenshot capture, Maestro UI automation, and debug log analysis. Follow these procedures exactly.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.