Tabularis is an open-source desktop application for connecting to and working with databases through SQL, including PostgreSQL, MySQL/MariaDB, SQLite, DuckDB, ClickHouse, Redis and Firestore. It is used for database exploration, querying, SQL notebooks and visual query-plan analysis, and includes an MCP server that lets Claude, Cursor and Devin access schemas and run queries.
Borrowing it
Nothing to install: this file belongs to TabularisDB/tabularis. 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/TabularisDB/tabularis/main/.claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.mdgit clone --depth 1 https://github.com/TabularisDB/tabularisWrote 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/tabularisdb/tabularis/gitnexus-impact-analysis)<a href="https://agentmods.dev/skills/tabularisdb/tabularis/gitnexus-impact-analysis"><img src="https://agentmods.dev/badge/skills/tabularisdb/tabularis/gitnexus-impact-analysis/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/tabularisdb/tabularis/gitnexus-impact-analysis"><img src="https://agentmods.dev/badge/skills/tabularisdb/tabularis/gitnexus-impact-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00755 |
| Opus 5.5 | $0.00020 | $0.00302 |
| Sonnet 5.5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
gitnexus-impact-analysis 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- gitnexus-impact-analysis — 100% identical, 0 lines differ
- gitnexus-impact-analysis — 100% identical, 0 lines differ
- gitnexus-impact-analysis — 100% identical, 0 lines differ
- gitnexus-impact-analysis — 100% identical, 0 lines differ
- gitnexus-impact-analysis — 100% identical, 0 lines differ
- gitnexus-impact-analysis — 100% identical, 0 lines differ
- gitnexus-impact-analysis — 100% identical, 0 lines differ
- gitnexus-impact-analysis — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impact Analysis with GitNexus
When to Use
- "Is it safe to change this function?"
- "What will break if I modify X?"
- "Show me the blast radius"
- "Who uses this code?"
- Before making non-trivial code changes
- Before committing — to understand what your changes affect
Workflow
1. impact({target: "X", direction: "upstream"}) → What depends on this
2. READ gitnexus://repo/{name}/processes → Check affected execution flows
3. detect_changes() → Map current git changes to affected flows
4. Assess risk and report to user
If "Index is stale" → run
node .gitnexus/run.cjs analyzein terminal.
Checklist
- [ ] impact({target, direction: "upstream"}) to find dependents
- [ ] Review d=1 items first (these WILL BREAK)
- [ ] Check high-confidence (>0.8) dependencies
- [ ] READ processes to check affected execution flows
- [ ] detect_changes() for pre-commit check
- [ ] Assess risk level and report to user
Understanding Output
| Depth | Risk Level | Meaning |
|---|---|---|
| d=1 | WILL BREAK | Direct callers/importers |
| d=2 | LIKELY AFFECTED | Indirect dependencies |
| d=3 | MAY NEED TESTING | Transitive effects |
Risk Assessment
| Affected | Risk |
|---|---|
| <5 symbols, few processes | LOW |
| 5-15 symbols, 2-5 processes | MEDIUM |
| >15 symbols or many processes | HIGH |
| Critical path (auth, payments) | CRITICAL |
Tools
impact — the primary tool for symbol blast radius:
impact({
target: "validateUser",
direction: "upstream",
minConfidence: 0.8,
maxDepth: 3
})
→ d=1 (WILL BREAK):
- loginHandler (src/auth/login.ts:42) [CALLS, 100%]
- apiMiddleware (src/api/middleware.ts:15) [CALLS, 100%]
→ d=2 (LIKELY AFFECTED):
- authRouter (src/routes/auth.ts:22) [CALLS, 95%]
detect_changes — git-diff based impact analysis:
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 · 98 lines · 50 tokens per session scan A 09e529505da1
gitnexus-impact-analysis is a skill published in the GitHub repository TabularisDB/tabularis (5,265 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 755 once invoked, about $0.0002 per session on Opus 5.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
read-only-investigation
Use this reference when a user asks to investigate unexpected rows, a failed read, a slow query or a metadata mismatch without changing database state.
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
readmd-code-analysis
Use when source code or a configuration file needs a factual logic and risk analysis.
wsl-vscode-doctor
Diagnose and fix code . failing to launch, or opening a disconnected Windows-side VS Code instead of a WSL-connected (Remote-WSL) window, in a herdr-spawned WSL shell.
rca
Disciplined root-cause analysis for diagnosing why something is broken. Use whenever the user is debugging a bug, regression, incident, outage, flaky or intermittent behavior, a failing test, or asks "why is X happening" / "why did this break" / "whats causing this" — even if they never say the words "root cause." It…
dsh-autofix
A recovery guide for common DeepSeek Harness failures, such as missing commands, stale text, unavailable history, or failed installation. It examines the current error and applies a small, matching recovery step.