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 grovs-io/mcp --skill grovs-configure-platformgit clone --depth 1 https://github.com/grovs-io/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/grovs-io/mcp/grovs-configure-platform)<a href="https://agentmods.dev/skills/grovs-io/mcp/grovs-configure-platform"><img src="https://agentmods.dev/badge/skills/grovs-io/mcp/grovs-configure-platform/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/grovs-io/mcp/grovs-configure-platform"><img src="https://agentmods.dev/badge/skills/grovs-io/mcp/grovs-configure-platform.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.00060 | $0.00598 |
| Opus 5 | $0.00030 | $0.00299 |
| Sonnet 5 | $0.00012 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
grovs-configure-platform 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grovs: Configure Platform Settings
Two tools, two different IDs
| Tool | ID type | Purpose |
|---|---|---|
configure_sdk |
instance_id (string) | Platform identity: bundle IDs, team IDs, package names, fingerprints |
configure_redirects |
project_id (string) | Where users land: App Store URL, Play Store URL, fallback website |
These are different strings. Both come from get_status. Passing the wrong one is the #1 mistake.
Always show current state first
Call get_status and show the user what's currently configured before making changes. Prevents accidental overwrites.
Redirect fields take full URLs
Pass "https://apps.apple.com/app/id123456" — not symbolic names like "app_store". The schema validates with z.url().
Platform requirements
iOS Universal Links require both:
ios_bundle_id(e.g.,com.company.app)ios_team_id(Apple Developer Team ID)
Missing either → deep links won't open the app on iOS. ios_app_store_id is optional (only for App Store redirects).
Android App Links require both:
android_package_name(e.g.,com.company.app)android_sha256_fingerprints(array of strings fromkeytool -list -vor Play Console)
Missing either → deep links won't open the app on Android.
Both tools are partial updates
Only send fields the user wants to change. Omitted fields stay unchanged.
Example
User: "Add Android support, package is com.foodies.android, here's the fingerprint: AB:CD:EF:..."
configure_sdk(
instance_id: "x7k2",
android_package_name: "com.foodies.android",
android_sha256_fingerprints: ["AB:CD:EF:..."]
)
Don't resend the iOS fields — they stay as-is.
If something fails
- Error on
configure_sdk→ most likely you passed a project_id instead of instance_id - Error on
configure_redirects→ check you passed a valid URL (not a bare domain like"example.com", must be"https://example.com") - Per-link redirect overrides → that's
custom_redirectsoncreate_link/update_link, not these tools
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.
- 8d ago First seen · 66 lines · 60 tokens per session scan A 7839c2d47679
grovs-configure-platform is a skill published in the GitHub repository grovs-io/mcp (2 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 598 once invoked, about $0.0003 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
xcode-build-orchestrator
Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to xcode-build-fixer, and re-benchmarking after changes. Use when a developer wants an end-to-end build optimization workflow, asks to speed…
xcode-build-fixer
Implement approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when the developer has reviewed an optimization plan and approved specific changes, or when there is a clear list of build-setting or source-level fixes to apply and verify.
xcode-project-analyzer
Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis…
omh-apple-design
This is a Hermes-native apple-design workflow skill.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.