agentsclimarketplace
Sign in

Tool permission audit

Skill alexzhu0/agent-ready-skills/skills/tool-permission-audit

Use when auditing AI-agent tool permissions, command policies, connector access, GitHub actions, file-system scopes, or automation rules for risk, approval gates, and least-privilege controls.From its SKILL.md

Install
npx -y skills add alexzhu0/agent-ready-skills --skill tool-permission-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 268 tokens by cl100k_base, as published. Nobody here has run it

Tool Permission Audit

Purpose

Review an agent's tools and permission policy for unsafe access, unclear gates, and least-privilege gaps.

Fit

  • Use when an agent can read/write files, call connectors, run commands, publish, or touch credentials.
  • Do not use when the agent has no tool access and only produces plain text.

Inputs

  • Tool list, command allowlist, connector scopes, system instructions, or policy text.
  • User expectations for autonomy, external writes, destructive actions, and credentials.
  • Known environment restrictions.

Workflow

  1. Inventory tools and classify their side effects.
  2. Separate read-only, local write, external write, credential, and destructive actions.
  3. Check whether approval gates match the risk.
  4. Identify overbroad scopes and ambiguous wording.
  5. Recommend a least-privilege policy patch.

Output

Produce Markdown with:

  • Permission Matrix
  • Risk Summary
  • Approval Gates
  • Overbroad Access
  • Policy Gaps
  • Recommended Patch
  • Residual Risks

Validation

  • Public or external writes are clearly gated.
  • Destructive commands are not treated as normal execution.
  • Credential handling is explicit.
  • Local reversible actions are separated from irreversible actions.
  • Recommendations preserve useful autonomy where risk is low.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most audit compliance skills give in 268 tokens

Counted across 937 of the 1,487 authors here whose files we hold, read 2026-08-07

  • Fetch latest guidelines before each reviewin 43 of 937, across 3 files
  • Group findings by severityin 43 of 937
  • Check files against all fetched rulesin 42 of 937, across 2 files
  • Output findings in terse file:line formatin 41 of 937, across 3 files
  • Ask user which files to review if none specifiedin 41 of 937, across 3 files
  • Read specified files or prompt user for filesin 39 of 937, across 1 file
  • Generate the audit reportin 33 of 937, across 30 files
  • Assign a severity to every findingin 25 of 937
  • Run automated accessibility scansin 23 of 937, across 13 files
  • Output a markdown audit reportin 22 of 937
  • Map findings to WCAG criteriain 20 of 937, across 10 files
  • Confirm audit scopein 19 of 937, across 9 files

Said here and by no other author read

  • inventory tools and classify their side effects
  • separate read-only, write, credential, and destructive actions
  • check whether approval gates match the risk
  • identify overbroad scopes and ambiguous wording
  • recommend a least-privilege policy patch
  • produce markdown containing the specified sections

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.