Borrowing it
Nothing to install: this file belongs to iBrain-BVBA/gutt-claude-code-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iBrain-BVBA/gutt-claude-code-plugin/main/.claude/commands/lint-test.mdgit clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-pluginWrote 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/ibrain-bvba/gutt-claude-code-plugin/lint-test)<a href="https://agentmods.dev/commands/ibrain-bvba/gutt-claude-code-plugin/lint-test"><img src="https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/lint-test/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/ibrain-bvba/gutt-claude-code-plugin/lint-test"><img src="https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/lint-test.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.00000 | $0.00536 |
| Opus 5.5 | $0.00000 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
lint-test 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 1mo 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.
What it actually says
Lint and Test Command
/lint-test - Run linting and tests before committing.
Usage
/lint-test
/lint-test --fix # Auto-fix lint issues
/lint-test --watch # Watch mode for tests
Workflow
Step 1: Check Memory for Project Standards
search_memory_nodes(query="coding standards linting", entity="WorkingAgreement", max_nodes=5)
Step 2: Run Linting
Python:
# Format check
black --check src/ tests/
# Lint
flake8 src/ tests/
# Type check
mypy src/
TypeScript/JavaScript:
# Lint
npm run lint
# Type check (TypeScript)
npm run typecheck
Step 3: Run Tests
Python:
pytest tests/ -v --tb=short
TypeScript/JavaScript:
npm test
Step 4: Report Results
## Lint & Test Results
### Linting
- Formatter: PASS (or X files need formatting)
- Linter: PASS (or X issues found)
- Type check: PASS (or X type errors)
### Tests
- Total: X tests
- Passed: X
- Failed: X
- Skipped: X
### Verdict: READY TO COMMIT / NEEDS FIXES
Auto-Fix Mode (--fix)
# Python
black src/ tests/
isort src/ tests/
# JavaScript/TypeScript
npm run lint -- --fix
Default Commands by Language
| Language | Lint | Test |
|---|---|---|
| Python | black --check . && flake8 . && mypy . |
pytest -v |
| TypeScript | npm run lint && npm run typecheck |
npm test |
| JavaScript | npm run lint |
npm test |
| Go | go fmt ./... && go vet ./... |
go test ./... |
Pre-Commit Integration
If .pre-commit-config.yaml exists, run:
pre-commit run --all-files
Exit Codes
0- All checks pass, ready to commit1- Lint or test failures, needs fixes
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.
- 1mo ago First seen · 111 lines · 0 tokens per session scan A 44633a0d58e5
lint-test is a command published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 536 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.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.