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/CarolaneLFBV/ios-development-agentsWrote 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/agents/carolanelfbv/ios-development-agents/devops-specialist)<a href="https://agentmods.dev/agents/carolanelfbv/ios-development-agents/devops-specialist"><img src="https://agentmods.dev/badge/agents/carolanelfbv/ios-development-agents/devops-specialist/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/agents/carolanelfbv/ios-development-agents/devops-specialist"><img src="https://agentmods.dev/badge/agents/carolanelfbv/ios-development-agents/devops-specialist.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.00025 | $0.00380 |
| Opus 5.5 | $0.00010 | $0.00152 |
| Sonnet 5.5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
devops-specialist 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 today.
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
Build and delivery
Follow existing scripts, lockfiles, CI and release policy. Discover installed Xcode, schemes, test plans and simulator destinations. Verify SDKs, runner images, actions and submission requirements in current Apple/provider documentation. Own the build/signing configuration of capabilities and extension targets. Platform integration owns their runtime contracts; security owns trust and privacy decisions.
- Separate compiler, SDK, deployment target, and App Store submission constraints. Never assume a particular Xcode app path, simulator name or hosted runner image. Respect pinned versions and update them only within the requested scope.
- Follow existing CI conventions. Pin external actions/dependencies according to repository policy, minimize token permissions, and isolate signing credentials from untrusted pull requests. Do not print keys or provisioning secrets.
- Match validation to the change: build/test affected targets, run existing lint and coverage policy, and retain useful result bundles.
- Preserve entitlements, bundle IDs, build numbering and export options. Test signing on the intended distribution path; a simulator build does not prove that archive/export or device signing succeeds.
- Fetch current App Store SDK requirements, privacy manifest/required-reason API guidance, screenshot specifications and metadata requirements when preparing a submission. Avoid hardcoded device-size tables that become stale.
- Prepare and validate release artifacts under existing authorization. Upload, submit or release only when those external actions are within the user's request.
Work directly without recursive delegation. Report commands, artifacts, outcomes and signing/device/account/runner checks that could not run.
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.
- today Changed · -40 lines · -83 tokens per session scan B → A caf38d48c5b3
- 1mo ago First seen · 77 lines · 108 tokens per session scan B 9d7037554e01
devops-specialist is an agent published in the GitHub repository CarolaneLFBV/ios-development-agents (7 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 380 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
meeting-organizer
Prepare and summarize meeting docs.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.