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 skills add IvanLutsenko/awac-ai-agent-plugins --skill install-permissionsgit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-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/ivanlutsenko/awac-ai-agent-plugins/install-permissions)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/install-permissions"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/install-permissions/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/skills/ivanlutsenko/awac-ai-agent-plugins/install-permissions"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/install-permissions.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.00044 | $0.01630 |
| Opus 5.5 | $0.00018 | $0.00652 |
| Sonnet 5.5 | $0.00009 | $0.00326 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade B, and why
crashlytics-install-permissions 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 9d 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.
- label: "User-level (~/.claude/settings.json)" How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Converted from Claude Code command
/install-permissions. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex. Helper scripts ship in this skill's ownscripts/directory. Replace<this skill directory>with the path Codex reported when it loaded this skill — a bare relative path would resolve against the repository under review instead.
Install Crashlytics permissions
Adds the Crashlytics plugin's read-only Bash and MCP tools to your settings.json
allowlist so /crashlytics:crash-report runs without permission prompts.
What gets added — strictly read-only operations:
- git:
status,log,blame,diff,show,fetch,branch,remote,ls-tree,ls-files,rev-parse,merge-base - crashlytics scripts (validate-report.py, fetch-crash-data.py, check-prerequisites.sh)
- MCP read tools:
crashlytics_get_*,crashlytics_list_*,crashlytics_batch_get_events,crashlytics_get_report,firebase_get_*,firebase_list_*
What is NEVER added — write/auth/destructive operations:
git push,git commit,git reset,git rebase,git cleancrashlytics_update_issue,crashlytics_create_note,crashlytics_delete_notefirebase_login,firebase_logout,firestore_*,auth_*,storage_*,messaging_*,realtimedatabase_*,remoteconfig_*
Step 1: Choose scope
AskUserQuestion:
questions:
- question: "Where to install the allowlist?"
header: "Scope"
options:
- label: "User-level (~/.claude/settings.json)"
description: "Applies in every project. Recommended if you use the plugin in multiple repos."
- label: "Project-level (.claude/settings.local.json)"
description: "Only this project. Safer if you don't want global allowance."
multiSelect: false
If User-level → SETTINGS_PATH = ~/.claude/settings.json.
If Project-level → SETTINGS_PATH = .claude/settings.local.json (mkdir -p .claude if missing).
Step 2: Read current settings
What ships with it
3 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.
- 9d ago Changed · +7 lines 4fcfcfdd345a
- 1mo ago First seen · 171 lines · 44 tokens per session scan B 38655f0757d0
crashlytics-install-permissions is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 1,630 once invoked, about $0.0002 per session on Opus 5.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-09-05.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…