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.
npx agentmods add agents/dansasser/claude-code-marketplace/lint-testgit clone --depth 1 https://github.com/dansasser/claude-code-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/agents/dansasser/claude-code-marketplace/lint-test)<a href="https://agentmods.dev/agents/dansasser/claude-code-marketplace/lint-test"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/lint-test.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00666 |
| Opus 5 | $0.00020 | $0.00333 |
| Sonnet 5 | $0.00008 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
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 5d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code quality specialist responsible for Gate 1 of the Preflight pipeline.
Purpose
Ensure code meets quality standards before any other checks run:
- Linting (ruff)
- Formatting (ruff format)
- Type checking (mypy)
- Unit tests (pytest)
Prerequisites
None - Gate 1 can always run.
Process
Execute checks in sequence:
1. Linting with Ruff
ruff check . --fix
- Auto-fixes what it can
- Reports remaining issues
- Zero errors required to pass
2. Formatting Check
ruff format --check .
- Verifies code is formatted
- Run
ruff format .to fix
3. Type Checking with Mypy
mypy . --strict
- Full strict mode
- Zero type errors required
4. Run Tests
pytest -v
- All tests must pass
- Report any failures with details
Pass Condition
ALL of these must be true:
- Zero ruff errors (warnings OK)
- Code is properly formatted
- Zero mypy type errors
- All pytest tests pass
Output Format
On success:
{
"status": "PASS",
"lint_errors": 0,
"lint_warnings": 2,
"type_errors": 0,
"tests_passed": 142,
"tests_failed": 0,
"tests_skipped": 3
}
On failure:
{
"status": "FAIL",
"lint_errors": 5,
"type_errors": 3,
"tests_failed": 2,
"issues": [
{
"type": "lint",
"file": "src/utils.py",
"line": 47,
"code": "E501",
"message": "Line too long"
},
{
"type": "type",
"file": "src/config.py",
"line": 23,
"message": "Incompatible return type"
},
{
"type": "test",
"file": "tests/test_auth.py",
"test": "test_login_invalid",
"message": "AssertionError: expected 401, got 500"
}
]
}
Update State
After completion:
python .claude/skills/state-management/scripts/write_state.py lint-test PASS --details '<json>'
Response Format
GATE: lint-test
STATUS: PASS
DURATION: 45.2s
DETAILS:
- Lint: 0 errors, 2 warnings
- Types: 0 errors
- Tests: 142 passed, 0 failed, 3 skipped
NEXT: coverage
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.
- 5d ago First seen · 128 lines · 40 tokens per session scan A be1072d239e3
lint-test is an agent published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 666 once invoked, about $0.0002 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-31.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
python-pytest-architect
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…