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 bug-reprogit 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/bug-repro)<a href="https://agentmods.dev/skills/hoainho/podium-mcp/bug-repro"><img src="https://agentmods.dev/badge/skills/hoainho/podium-mcp/bug-repro/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/hoainho/podium-mcp/bug-repro"><img src="https://agentmods.dev/badge/skills/hoainho/podium-mcp/bug-repro.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.00042 | $0.00302 |
| Opus 5 | $0.00021 | $0.00151 |
| Sonnet 5 | $0.00008 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
bug-repro 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 9d 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 → bug description / repro steps
Execute in this exact order (await each call):
record_start— saveTo/tmp/repro-<BUNDLE_ID>.mp4inspect_screenon the UDID — capture the starting state- Author and call
run_flowwith an inline Maestro YAML that encodes the repro steps. Use only selectors from step 2. record_stopmetro_logs— durationMs 4000, maxLogs 100 — capture console output around the reprocrash_list— udid UDID, sinceHours 1 — check for new crashes
Summarize:
- Did the bug reproduce? (REPRODUCED / NOT REPRODUCED / INCONCLUSIVE)
- Video path + sizeBytes from record_stop
- Relevant log lines (errors/warnings only)
- Any new crash entry (exception type + top frame)
- Root-cause hypothesis with evidence
If Metro is not running, note it and skip step 5 — do not fail the whole repro.
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.
- 9d ago First seen · 27 lines · 42 tokens per session scan A 4c054379d343
bug-repro is a skill published in the GitHub repository hoainho/podium-mcp (4 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 302 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
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.