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.
npx agentmods add skills/shipwithai/shipwithai-plugins/setup-permissionsnpx skills add ShipWithAI/shipwithai-plugins --skill setup-permissionsgit clone --depth 1 https://github.com/ShipWithAI/shipwithai-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/skills/shipwithai/shipwithai-plugins/setup-permissions)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/setup-permissions"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/setup-permissions.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00844 |
| Opus 5 | $0.00023 | $0.00422 |
| Sonnet 5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
setup-permissions 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-permissions
Configures .claude/settings.json → permissions.allow and permissions.deny.
Flags
Check flags first — they override Mode Detection behavior:
--stack <name>— skip auto-detection, use the provided stack preset directly--preset-only— apply the matched preset without asking customization questions
Mode Detection
If --stack flag is provided → skip detection, use that stack value directly
Otherwise:
Read .claude/starter-context.json if it exists
→ Exists:
- Use fields: stack, permissions.preset, permissions.disallowed_tools, permissions.readonly_paths
- For each field that is null or missing → ask for that field only
→ Not found (standalone):
- Auto-detect stack from project files
- If detection fails → default to "general" preset, inform user:
"Could not detect stack — using the general (read-only) preset. Pass --stack to override."
- Show preset → confirm or customize (unless --preset-only is set)
Load Preset
Read settings-presets.json, match by stack:
nodejs → allow: Read, Write, Edit, Grep, Glob, Bash(npm:*), Bash(npx:*), Bash(node:*), Bash(git:*)
python → allow: Read, Write, Edit, Grep, Glob, Bash(python:*), Bash(pip:*), Bash(pytest:*), Bash(git:*)
golang → allow: Read, Write, Edit, Grep, Glob, Bash(go:*), Bash(git:*)
java → allow: Read, Write, Edit, Grep, Glob, Bash(mvn:*), Bash(gradle:*), Bash(java:*), Bash(git:*)
rust → allow: Read, Write, Edit, Grep, Glob, Bash(cargo:*), Bash(git:*)
general → allow: Read, Grep, Glob (Write/Edit/Bash not allowed until user explicitly adds them)
Show the preset with a one-line explanation per rule. Then ask:
- "Any tools Claude should NOT use?" → add to
deny - "Any paths that should be read-only?" → add path-scoped deny rules (see Output Format)
Skip both questions if --preset-only is set.
Multi-stack projects (e.g., Node frontend + Python backend): apply the union of both presets. Ask: "I detected both Node and Python — should I allow tools for both stacks?"
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 93 lines · 47 tokens per session scan A a2bd31d3f5a5
setup-permissions is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 22d ago), licensed MIT. It adds 47 tokens to every session and 844 once invoked, about $0.0002 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.
Other skills, from other repositories
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.