agentmods.dev

aidevops: Command for Claude Code

.agents/scripts/commands/local-permissions-check.md

local-permissions-check is a command for Claude Code from marcusquinn/aidevops. It costs 20 tokens per session (440 once invoked), scanned A, original, MIT.

A read-only check of the permissions and runtime limits that may affect aidevops on macOS, Linux, Windows, and WSL (Windows Subsystem for Linux).

In plain words
What is it for?
Use it to diagnose local permission problems, produce machine-readable evidence, or list detected host and editor apps.
Why use it?
It shows whether privacy, sandbox, file-system, command-execution, or screen-control restrictions could prevent a workflow from working, without changing those settings.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: agent in frontmatter; mentions subagents; installed under .agents/ (shared by several agents).

This is marcusquinn/aidevops's own configuration. It tells Claude Code how to work on aidevops itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aidevops configures →

Part of the aidevops plugin — 13 skills, 128 commands shipped together

not rated 392repo +1 today A scan 20 tokens original MIT
View source ↗ marcusquinn/aidevops aidevops.sh
Reuse

Borrowing it

Nothing to install: this file belongs to marcusquinn/aidevops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/marcusquinn/aidevops/main/.agents/scripts/commands/local-permissions-check.md
Clone the repo
git clone --depth 1 https://github.com/marcusquinn/aidevops

Made for: Claude Code.

Or install aidevops, the plugin that ships this one along with the rest of its 13 skills, 128 commands.

Wrote 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.

agentmods badge for local-permissions-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/marcusquinn/aidevops/local-permissions-check.svg)](https://agentmods.dev/commands/marcusquinn/aidevops/local-permissions-check)
Your own site
<a href="https://agentmods.dev/commands/marcusquinn/aidevops/local-permissions-check"><img src="https://agentmods.dev/badge/commands/marcusquinn/aidevops/local-permissions-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 440 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00020 $0.00440
Opus 5 $0.00010 $0.00220
Sonnet 5 $0.00004 $0.00088
Haiku 4.5 $0.00002 $0.00044

Measured 8d ago against content hash e79b996d84a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

local-permissions-check 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 8d 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.

.agents/scripts/commands/local-permissions-check.md · 55 lines

What it actually says

Run a read-only local permission/capability diagnostic for aidevops workflows. macOS reports TCC host-app privacy state; Linux, Windows, and WSL report safe session, sandbox, filesystem, execution-policy, and UI automation caveats.

Arguments: $ARGUMENTS

Procedure

  1. Run the deterministic helper first:

    ~/.aidevops/agents/scripts/local-permissions-check-helper.sh report $ARGUMENTS

  2. If the user asks for machine-readable evidence:

    ~/.aidevops/agents/scripts/local-permissions-check-helper.sh json $ARGUMENTS

  3. To list detected host/editor apps only:

    ~/.aidevops/agents/scripts/local-permissions-check-helper.sh apps

Safety

  • Read-only by default: do not reset TCC, grant permissions, or intentionally trigger prompts; do not change Windows execution policy, start services, or use sudo/admin privileges.
  • macOS permissions apply to the host app that launched aidevops, not to child bash, zsh, opencode, or aidevops processes.
  • For Tabby-launched sessions with Trash cleanup failures, check Full Disk Access for Tabby in System Settings → Privacy & Security.
  • Linux Wayland screenshots/UI automation often require desktop portals; X11, Flatpak, Snap, containers, and WSL have separate boundaries.
  • Windows/WSL reports are advisory unless a safe shell signal exists; protected folders and Defender Controlled Folder Access usually require manual checking.

Verification references

  • .agents/workflows/local-permissions-check.md
  • .agents/tools/security/local-permissions-check.md
  • .agents/scripts/tests/test-local-permissions-check-helper.sh
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. 8d ago First seen · 55 lines · 20 tokens per session scan A e79b996d84a3

Subscribe to this mod's changes

local-permissions-check is a command published in the GitHub repository marcusquinn/aidevops (392 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 440 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-30.

DevOps and cloudagentsagents-mdaiai-agentsdevops-tools
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens