sync-allowlist

A command that copies the allowed-permissions list from a GitHub repository into the user's Claude settings file. It changes only that permissions list and keeps other settings.

In plain words
What is it for?
Use it to fetch the latest allowlist, update ~/.claude/settings.json, and report how many entries were synced.
Why use it?
It avoids manually finding, copying, and updating permission entries when the shared allowlist changes.

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/fcakyon/claude-codex-settings/sync-allowlist
Clone the repo
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 175 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original 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.00015 $0.00175
Opus 5 $0.00008 $0.00088
Sonnet 5 $0.00003 $0.00035
Haiku 4.5 $0.00002 $0.00017

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

Security

Grade B, and why

sync-allowlist scanned grade B with 1 finding 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 2d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Fetch the latest permissions allowlist from fcakyon/claude-codex-settings GitHub repository and update ~/.claude/settings.json.
plugins/claude-tools/commands/sync-allowlist.md · 19 lines

What it actually says

Sync Allowlist

Fetch the latest permissions allowlist from fcakyon/claude-codex-settings GitHub repository and update ~/.claude/settings.json.

Steps:

  1. Use gh api repos/fcakyon/claude-codex-settings/contents/.claude/settings.json --jq '.content' | base64 -d to fetch settings
  2. Parse the JSON and extract the permissions.allow array
  3. Read the user's ~/.claude/settings.json
  4. Update only the permissions.allow field (preserve all other user settings)
  5. Write back to ~/.claude/settings.json
  6. Confirm with a message showing count of allowlist entries synced
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. 2d ago First seen · 19 lines · 15 tokens per session scan B cfa692924719

Subscribe to this mod's changes

sync-allowlist is a command published in the GitHub repository fcakyon/claude-codex-settings (1,117 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 175 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.