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.
git clone --depth 1 https://github.com/zurche/agent-skillsWrote 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/zurche/agent-skills/android-release-bump)<a href="https://agentmods.dev/plugins/zurche/agent-skills/android-release-bump"><img src="https://agentmods.dev/badge/plugins/zurche/agent-skills/android-release-bump/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/plugins/zurche/agent-skills/android-release-bump"><img src="https://agentmods.dev/badge/plugins/zurche/agent-skills/android-release-bump.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
android-release-bump 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 1mo 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": "android-release-bump",
"version": "1.1.0",
"description": "Reusable Android release workflow with version bumps, Play release notes, verification, optional headless emulator QA, and optional Play upload.",
"author": {
"name": "Alejandro Zurcher"
},
"homepage": "https://github.com/zurche/agent-skills",
"repository": "https://github.com/zurche/agent-skills",
"license": "MIT",
"keywords": [
"android",
"release",
"gradle",
"play-store"
],
"skills": "./skills"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 91 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 19 lines scan A d3f9a3c2660e
android-release-bump is a plugin published in the GitHub repository zurche/agent-skills (1 stars, last pushed 6mo 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
asc
Production workflows for shipping apps with the unofficial App Store Connect CLI, including builds, TestFlight, metadata, submissions, signing, screenshots, and Apple Ads.
oss
Open-source maintenance: analyse, review, resolve, release-readiness, and setup skills with four specialist agents.
ensemble-git
Git workflow automation and conventional commits.
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.…
asc-mcp
Run an App Store release from a conversation: review status, reviews and sales, metadata, screenshots, builds, TestFlight, in-app purchases, submit and release. A local MCP server for App Store Connect plus a review-triage skill.
ooda-loop marketplace
Plugin marketplace listing 1 plugin: ooda-loop.