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.
curl -O https://raw.githubusercontent.com/ubie-oss/dbt-data-privacy/main/.claude/skills/test-and-fix/SKILL.mdgit clone --depth 1 https://github.com/ubie-oss/dbt-data-privacyWrote 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/skills/ubie-oss/dbt-data-privacy/test-and-fix)<a href="https://agentmods.dev/skills/ubie-oss/dbt-data-privacy/test-and-fix"><img src="https://agentmods.dev/badge/skills/ubie-oss/dbt-data-privacy/test-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.
<a href="https://agentmods.dev/skills/ubie-oss/dbt-data-privacy/test-and-fix"><img src="https://agentmods.dev/badge/skills/ubie-oss/dbt-data-privacy/test-and-fix.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.00025 | $0.00639 |
| Opus 5 | $0.00013 | $0.00319 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
test-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 10d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test and Fix
Purpose
This skill provides an autonomous loop to identify, analyze, and fix test failures within the integration_tests directory using the project's make commands.
Loop Logic
- Identify: Run tests from the
integration_testsdirectory.- Agent must make sure what type of test the user wants to run (unit or integration), becaues it takes a long time to run all tests.
make test: Runs all unit and integration tests (both dbt-core and dbt-fusion). This is the standard command for a full verification.make run-unit-tests: Runs all unit tests (both core and fusion).make run-integration-tests: Runs all integration tests (both core and fusion).- For targeted debugging, use granular sub-targets:
make run-unit-tests-core/make run-unit-tests-fusionmake run-integration-tests-core/make run-integration-tests-fusion
- Analyze: Examine the test output and logs to understand which tests are failing.
- Check the
logs/dbt.loginintegration_tests/for detailed dbt execution logs. - For macro failures, inspect the generated SQL and compare it with expected BigQuery syntax.
- Note: BigQuery is the only supported warehouse in this repository.
- Check the
- Plan Fix: Before applying any fix, create an MVP scaffold that delivers the smallest valuable slice of the fix.
- Define acceptance criteria for the fix.
- Create a plan in memory to track the fix progress.
- Execute & Test:
- Implement the MVP scaffold.
- Run the relevant tests immediately (e.g.,
cd integration_tests && make run-unit-tests-core). - Only add details and enhancements after the scaffold tests pass.
- Verify: Re-run the tests.
- If all checks pass: Termination.
- If new or remaining failures exist: Analyze the failure and repeat the loop.
Termination Criteria
- All relevant tests exit with code 0 (all checks passed).
- Reached max iteration limit of 5 attempts.
- No progress being made (same errors persisting despite fix attempts).
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.
- 10d ago First seen · 54 lines · 25 tokens per session scan A b9b77164bd8d
test-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 25 tokens to every session and 639 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 skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.