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.
git clone --depth 1 https://github.com/Marcel-Bich/marcel-bich-claude-marketplaceWrote 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/commands/marcel-bich/marcel-bich-claude-marketplace/permissions)<a href="https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/permissions"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/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/commands/marcel-bich/marcel-bich-claude-marketplace/permissions"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/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.00024 | $0.03925 |
| Opus 5.5 | $0.00010 | $0.01570 |
| Sonnet 5.5 | $0.00005 | $0.00785 |
| Haiku 4.5 | $0.00002 | $0.00392 |
Grade A, and why
permissions 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dogma:permissions - Create Permissions File
Create or update DOGMA-PERMISSIONS.md to configure what Claude can do autonomously.
- Check if
DOGMA-PERMISSIONS.mdexists in project root - If exists, show current permissions and ask if user wants to update
- When updating, keep every existing
(§xxxx)id and add the template id (Step 4) to each recognized setting line or parsed heading that has none yet. Ids come only from the template /docs/permission-ids.md- never invent a new one. - When the file has no
## Inheritancesection yet, ask Step 1b and add it at the top of the<permissions>block.
- When updating, keep every existing
- If not exists, will create new file
Step 1b: Inheritance
Ask via AskUserQuestion whether this file inherits settings from a parent or workspace folder (default: yes, [x]):
- yes
[x](default): when Claude works in this project from another folder that has its own DOGMA-PERMISSIONS.md (for example a parent or workspace folder the session was started in), every setting this file does not define is taken from that folder's file. Settings defined here always win. - no
[ ]: only this file counts; settings it does not define use dogma's defaults.
Explain briefly which file applies (resolution order "target of the action > pinned project > session folder") with the example from the template's Inheritance section below. A file without this checkbox behaves like [x].
Step 2: Git & File Permissions
Ask the user about each permission using AskUserQuestion. For each permission offer 3 choices:
- auto
[x]: Claude does it automatically - ask
[?]: Claude asks for confirmation first - deny
[ ]: Claude cannot do it (blocked)
Git Operations
git add
- auto: Claude can stage files for commits
- ask: Claude asks before staging
- deny: User must run
git addmanually
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.
- 14d ago Changed · +8 lines 1b318524b96b
- 19d ago Changed · +97 lines a7e45d2d860d
- 1mo ago First seen · 275 lines · 24 tokens per session scan A 4af760c6fd98
permissions is a command published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (12 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 3,925 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
context-stats
Display context window usage and token statistics.
deps-update
Audit and update dependencies safely.
security-scan
Run security audit on codebase.
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.