dbt-data-privacy: Skill for Claude Code

.claude/skills/lint-and-fix/SKILL.md

lint-and-fix is a skill for Claude Code from ubie-oss/dbt-data-privacy. It costs 31 tokens per session (351 once invoked), scanned A, original, Apache-2.0.

An automated loop that runs the project's lint checks, fixes reported code-style problems, and checks again.

In plain words
What is it for?
Use it to resolve linter failures across a codebase with the project's make lint command.
Why use it?
It removes the manual cycle of finding formatting and code-quality violations and verifying each fix.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is ubie-oss/dbt-data-privacy's own configuration. It tells Claude Code how to work on dbt-data-privacy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dbt-data-privacy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ubie-oss/dbt-data-privacy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ubie-oss/dbt-data-privacy/main/.claude/skills/lint-and-fix/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ubie-oss/dbt-data-privacy

Made for: Claude Code.

Wrote 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.

agentmods badge for lint-and-fix

README.md
[![agentmods](https://agentmods.dev/badge/skills/ubie-oss/dbt-data-privacy/lint-and-fix/github.svg)](https://agentmods.dev/skills/ubie-oss/dbt-data-privacy/lint-and-fix)
Your own site
<a href="https://agentmods.dev/skills/ubie-oss/dbt-data-privacy/lint-and-fix"><img src="https://agentmods.dev/badge/skills/ubie-oss/dbt-data-privacy/lint-and-fix/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.

agentmods 80×15 button for lint-and-fix

Your own site · 80×15
<a href="https://agentmods.dev/skills/ubie-oss/dbt-data-privacy/lint-and-fix"><img src="https://agentmods.dev/badge/skills/ubie-oss/dbt-data-privacy/lint-and-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 351 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00351
Opus 5 $0.00015 $0.00176
Sonnet 5 $0.00006 $0.00070
Haiku 4.5 $0.00003 $0.00035

Measured 11d ago against content hash 370dc8469096, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

lint-and-fix 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.

.claude/skills/lint-and-fix/SKILL.md · 38 lines

What it actually says

Lint and Fix

Purpose

This skill provides an autonomous loop to identify, fix, and verify linter violations in the codebase using the project's make lint command (which runs pre-commit).

Loop Logic

  1. Identify: Run make lint from the workspace root to list current violations.
  2. Analyze: Examine the linter output to understand which files and rules are failing.
  3. Fix: Apply targeted fixes for the identified violations.
    • Many linters in pre-commit (like black, ruff, prettier) can auto-fix issues.
    • If pre-commit auto-fixes files, review the changes.
    • If manual fixes are required, apply the minimum necessary change to resolve each error.
  4. Verify: Re-run make lint.
    • If all checks pass: Termination.
    • If new or remaining failures exist: Analyze the failure and repeat the loop.

Termination Criteria

  • make lint exits with code 0 (all checks passed).
  • Reached max iteration limit of 5 attempts.
  • No progress being made (same errors persisting despite fix attempts).

Examples

Scenario: Fixing formatting and imports

  1. make lint fails with ruff and black errors.
  2. Agent runs make lint again (some linters auto-fix).
  3. Agent reviews auto-fixed changes.
  4. make lint passes.
Changes

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.

  1. 11d ago First seen · 38 lines · 31 tokens per session scan A 370dc8469096

Subscribe to this mod's changes

lint-and-fix is a skill published in the GitHub repository ubie-oss/dbt-data-privacy (22 stars, last pushed 9d ago), licensed Apache-2.0. It adds 31 tokens to every session and 351 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-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens