Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Marcel-Bich/marcel-bich-claude-marketplace/plugin install dogmaWrote 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/ignore)<a href="https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/ignore"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/ignore/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/ignore"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/ignore.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.00011 | $0.01977 |
| Opus 5 | $0.00005 | $0.00988 |
| Sonnet 5 | $0.00002 | $0.00395 |
| Haiku 4.5 | $0.00001 | $0.00198 |
Grade A, and why
ignore 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 12d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dogma: Ignore Pattern Manager
You are executing the /dogma:ignore command. Your task is to add ignore patterns to multiple locations at once (.git/info/exclude, .gitignore, and optionally sync.md).
Step 1: Get Pattern(s) from User
The user provided: $ARGUMENTS
If patterns provided:
- Parse the input - patterns can be space-separated (e.g.,
.aider* .continue* .codeium*) - Split into individual patterns
- Confirm understanding with user:
I will add the following patterns: - .aider* - .continue* - .codeium* Is that correct? [Y/n]
If no patterns provided:
- Ask user: "Which pattern do you want to ignore? (e.g., .aider* or '.aider* .continue*' for multiple)"
- Wait for response
- Confirm understanding as above
Step 2: Process Each Pattern
For each pattern, execute Steps 2.1 through 2.4 sequentially. Track results for the final summary.
Initialize tracking:
RESULTS=() # Array to store results per pattern
Step 2.1: .git/info/exclude (local, unversioned)
Check if pattern already exists:
grep -qxF "<pattern>" .git/info/exclude 2>/dev/null
If pattern exists:
Pattern "<pattern>" already exists in .git/info/exclude.
Add to results: [OK] .git/info/exclude (already present)
If pattern does NOT exist: Ask user using AskUserQuestion:
Should I add "<pattern>" to .git/info/exclude?
.git/info/exclude is local and not versioned - ideal for personal ignore patterns.
[Y/n]
If user confirms (Y or empty):
echo "<pattern>" >> .git/info/exclude
Add to results: [OK] .git/info/exclude
If user declines:
Add to results: [--] .git/info/exclude (skipped)
Step 2.2: .gitignore (versioned)
Check if pattern already exists:
grep -qxF "<pattern>" .gitignore 2>/dev/null
If pattern exists:
Pattern "<pattern>" already exists in .gitignore.
Add to results: [OK] .gitignore (already present)
If pattern does NOT exist: Ask user using AskUserQuestion:
Should I add "<pattern>" to .gitignore?
.gitignore is versioned and applies to all team members.
[Y/n]
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.
- 12d ago First seen · 293 lines · 11 tokens per session scan A db215d8707f3
ignore is a command published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 1,977 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
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
ship
Complete PR workflow from commit to production with validation.
ship-deployment
This file contains platform-specific deployment and validation for /ship.