app-capabilities

A capability-checking command that decides whether a role may perform an operation on a particular path, such as reading or changing a file.

In plain words
What is it for?
It checks a role, requested operation, and path against the capability manifest before an agent is allowed to act.
Why use it?
It enforces permissions from an explicit allowlist instead of letting descriptive text grant extra access. Missing, denied, or out-of-scope permissions stop the operation.

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/vmobifystudio/app-dev-team/app-capabilities
Clone the repo
git clone --depth 1 https://github.com/vmobifystudio/app-dev-team
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 96 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00096
Opus 5 $0.00000 $0.00048
Sonnet 5 $0.00000 $0.00019
Haiku 4.5 $0.00000 $0.00010

Measured yesterday against content hash 5e85178da208, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

app-capabilities 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 yesterday.

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.

commands/app-capabilities.md · 12 lines

What it actually says

/app-capabilities — enforce role boundaries

Check a role before granting an operation on a path:

node "${CLAUDE_PLUGIN_ROOT}/scripts/capability-check.mjs" \
  --manifest "$CAPABILITY_MANIFEST" --role <role> --operation <operation> --path <path>

Missing, denied, or out-of-scope capabilities block. The manifest is the allowlist; prose in a role description cannot expand it.

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. yesterday First seen · 12 lines · 0 tokens per session scan A 5e85178da208

Subscribe to this mod's changes

app-capabilities is a command published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 96 tokens. 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.