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/lint)<a href="https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/lint"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/lint/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/lint"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/lint.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.00018 | $0.01800 |
| Opus 5 | $0.00009 | $0.00900 |
| Sonnet 5 | $0.00004 | $0.00360 |
| Haiku 4.5 | $0.00002 | $0.00180 |
Grade A, and why
lint 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude-Dogma: Lint & Format
You are executing the /dogma:lint command. Your task is to detect the project type and run appropriate linting and formatting tools on staged files before commit.
NON-INTERACTIVE: This command runs silently. Skip anything not installed. No questions asked.
For interactive setup, use /dogma:lint:setup instead.
Arguments
$ARGUMENTS- Optional path to check. If empty, checks only staged files
Step 1: Get Staged Files
IMPORTANT: Only process files that are staged for commit. This protects legacy code.
git diff --cached --name-only 2>/dev/null
If $ARGUMENTS is provided, use that path instead.
If no staged files, report "No staged files to lint" and exit successfully.
Step 2: Detect Project Type & Available Tools
Check what tools are actually available (not just configured):
# Project files
ls package.json Cargo.toml go.mod pyproject.toml composer.json Gemfile mix.exs 2>/dev/null || true
# Check installed tools
[ -f "node_modules/.bin/eslint" ] && echo "eslint: installed"
[ -f "node_modules/.bin/prettier" ] && echo "prettier: installed"
command -v cargo &>/dev/null && echo "cargo: installed"
command -v go &>/dev/null && echo "go: installed"
command -v ruff &>/dev/null && echo "ruff: installed"
command -v black &>/dev/null && echo "black: installed"
[ -f "vendor/bin/phpstan" ] && echo "phpstan: installed"
[ -f "vendor/bin/php-cs-fixer" ] && echo "php-cs-fixer: installed"
Step 3: Run Linting (find errors)
For each detected tool, run linting on staged files. Skip if not installed.
JavaScript/TypeScript (ESLint)
if [ -f "node_modules/.bin/eslint" ]; then
ESLINT_FILES=$(git diff --cached --name-only | grep -E '\.(js|jsx|ts|tsx|vue)$' || true)
[ -n "$ESLINT_FILES" ] && echo "$ESLINT_FILES" | xargs npx eslint 2>&1
fi
Rust (cargo clippy)
command -v cargo &>/dev/null && [ -f "Cargo.toml" ] && cargo clippy -- -D warnings 2>&1
Go (go vet / golangci-lint)
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 · 222 lines · 18 tokens per session scan A 3e1da306e6b4
lint is a command published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 1,800 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
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
hades-show-traces
Point the user to Charon, Hades' trace explorer.
perf
Structured performance investigation with baselines, profiling, and evidence-backed decisions.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
health-check
Run diagnostics on Claude Code toolkit configuration and status.
feature:bugfix
Systematic bug investigation and fixing workflow for existing features. Uses code-reviewer for deep analysis, code-consolidator for context, parallel web research for solutions, and atomic phase implementation with review gates.