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 fledgeling-co/fledgeling-pluginsnpx agentmods add plugins/fledgeling-co/fledgeling-plugins/atlas-publishgit clone --depth 1 https://github.com/fledgeling-co/fledgeling-pluginsWrote 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/fledgeling-co/fledgeling-plugins/atlas-publish)<a href="https://agentmods.dev/plugins/fledgeling-co/fledgeling-plugins/atlas-publish"><img src="https://agentmods.dev/badge/plugins/fledgeling-co/fledgeling-plugins/atlas-publish.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
atlas-publish 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 yesterday.
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": "atlas-publish",
"version": "2.1.2",
"description": "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 \u2014 ios.buildNumber sits inside that fingerprint, so a buildNumber bump alone forces a store release. Every irreversible step names the observable to read back, because a build tool, an upload and an MCP call all return success without having done anything. Gates report not-run as a third state beside passed and failed, which is how a cert-parity test that skips its only real assertion stops reading as a green gate. Eleven steps, each marked with the lanes it applies to and each with an abort path next to it. Draft is where automation stops: publishing to users is a founder action the skill will not take. The diff review that used to ship beside it is now the standalone code-review plugin.",
"author": {
"name": "Fledgeling",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 280 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.
- yesterday Changed c522f2db5da8
- 5d ago First seen · 10 lines scan A 09e67e4f0617
atlas-publish is a plugin published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed today), 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.
android-release-bump
Reusable Android release workflow with version bumps, Play release notes, verification, optional headless emulator QA, and optional Play upload.
ios
iOS plugin.
swift-performance-pro
Performance: Instruments, SwiftUI render cost, memory and retain cycles, launch time, lists.
apple-craft
Apple 플랫폼 개발 스킬 모음 — 일반 구현/디버깅(apple-craft), 코드 리뷰(apple-review), 장기 대규모 구현 하네스(apple-harness, Designer 2-way split), App Store 배포 자동화(appstore-deploy), Xcode MCP 연동, xcodebuild+xcsift 빌드 폴백, Xcode 26 번들 문서 20개 + Swift 6.3 보강 + Concurrency Supplement(SE-0461/0466/0433, 차단형 동기화 정책) 내장, Pencil 디자인 통합.
pr-tools
Safe git push and PR workflow skill that prevents pushing to merged or closed PRs.