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/commands/carolanelfbv/ios-development-agents/security)<a href="https://agentmods.dev/commands/carolanelfbv/ios-development-agents/security"><img src="https://agentmods.dev/badge/commands/carolanelfbv/ios-development-agents/security/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/commands/carolanelfbv/ios-development-agents/security"><img src="https://agentmods.dev/badge/commands/carolanelfbv/ios-development-agents/security.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.00015 | $0.00260 |
| Opus 5.5 | $0.00006 | $0.00104 |
| Sonnet 5.5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
security 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
/ios:security
Audit $ARGUMENTS using security specialist expertise. Report by default; work
directly unless delegation is explicitly requested.
--focus auth|storage|network|crypto|allselects scope (default: all).--fixapplies scoped fixes with behavior validation.--reportincludes evidence and mitigations.--owaspmaps findings to the current Mobile Top 10 edition and relevant MASVS controls.--complianceidentifies technical privacy/compliance questions requiring further review; it does not certify compliance.
Check assets, threat boundaries, Keychain access policies, credential lifecycle, ATS/trust, cryptographic key/nonce handling and sensitive logs. Use current Apple and OWASP sources for security details. Pinning needs a justified threat model and rotation strategy rather than a blanket requirement.
Name the OWASP edition used and keep findings consistent with that taxonomy.
Return severity-ranked findings with location, preconditions, impact, mitigation and verification. Redact sensitive values. State static/runtime coverage and gaps.
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 · -49 lines · -1 tokens per session 9bb597f7e5d2
- 1mo ago First seen · 75 lines · 16 tokens per session scan A c4b7f21273d8
security is a command published in the GitHub repository CarolaneLFBV/ios-development-agents (7 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 260 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.