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.01609 |
| Opus 5 | $0.00012 | $0.00805 |
| Sonnet 5 | $0.00005 | $0.00322 |
| Haiku 4.5 | $0.00002 | $0.00161 |
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 11d 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 — 275 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
- If not exists, will create new file
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
git commit
- auto: Claude can create commits autonomously
- ask: Claude asks before committing
- deny: User must create commits manually
git push
- auto: Claude can push to remote repositories
- ask: Claude asks before pushing (recommended)
- deny: User must push manually
File Operations
Delete files
- auto: Claude can run rm, unlink, git clean
- ask: Claude prompts for confirmation before delete
- deny: Deletion commands are logged to TO-DELETE.md for manual deletion
Step 3: Workflow Permissions
Ask about workflow automation settings.
3.1 Testing - When to run?
Ask: "When should tests be executed?"
Options (can select multiple):
- before commit
- before push
- on tasklist completion
Default: [x] before commit, [x] before push, [x] on tasklist completion
3.2 Testing - What to test?
Ask: "What should be tested?"
Options:
- relevant tests
- silent-failure check - finds code that swallows errors (empty catch, ignored promises)
Default: [x] relevant tests, [x] silent-failure check
3.3 Review - When?
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.
- 11d 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 (13 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,609 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.
Other commands, from other repositories
migrate
Generate and manage database migrations.
context-stats
Display context window usage and token statistics.
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.