signing-setup

A command for setting up code signing, which lets iOS and Android builds be installed or distributed with the required credentials. It configures iOS certificates and profiles with Match, plus an Android keystore.

In plain words
What is it for?
Use it when preparing iOS certificates and provisioning profiles or an Android keystore for a Flutter or other mobile app.
Why use it?
It removes the manual setup of platform signing credentials for mobile builds.

Command

Install

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.

agentmods
npx agentmods add commands/smicolon/ai-kit/signing-setup
Clone the repo
git clone --depth 1 https://github.com/smicolon/ai-kit
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,219 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.01219
Opus 5 $0.00013 $0.00609
Sonnet 5 $0.00005 $0.00244
Haiku 4.5 $0.00003 $0.00122

Measured 3d ago against content hash 6ebcfa300327, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

signing-setup 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 3d 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.

packs/flutter/commands/signing-setup.md · 210 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 210 lines · 25 tokens per session scan A 6ebcfa300327

Subscribe to this mod's changes

signing-setup is a command published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 3mo ago), with no licence file. It adds 25 tokens to every session and 1,219 once invoked, about $0.0001 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.