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-refactoring/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-refactoring)<a href="https://agentmods.dev/skills/tabularisdb/tabularis/gitnexus-refactoring"><img src="https://agentmods.dev/badge/skills/tabularisdb/tabularis/gitnexus-refactoring/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-refactoring"><img src="https://agentmods.dev/badge/skills/tabularisdb/tabularis/gitnexus-refactoring.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.00053 | $0.00962 |
| Opus 5.5 | $0.00021 | $0.00385 |
| Sonnet 5.5 | $0.00011 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
gitnexus-refactoring 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-refactoring — 100% identical, 8 lines differ
- gitnexus-refactoring — 100% identical, 0 lines differ
- gitnexus-refactoring — 100% identical, 10 lines differ
- gitnexus-refactoring — 100% identical, 10 lines differ
- gitnexus-refactoring — 100% identical, 10 lines differ
- gitnexus-refactoring — 100% identical, 0 lines differ
- gitnexus-refactoring — 100% identical, 10 lines differ
- gitnexus-refactoring — 100% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring with GitNexus
When to Use
- "Rename this function safely"
- "Extract this into a module"
- "Split this service"
- "Move this to a new file"
- Any task involving renaming, extracting, splitting, or restructuring code
Workflow
1. impact({target: "X", direction: "upstream"}) → Map all dependents
2. query({search_query: "X"}) → Find execution flows involving X
3. context({name: "X"}) → See all incoming/outgoing refs
4. Plan update order: interfaces → implementations → callers → tests
If "Index is stale" → run
node .gitnexus/run.cjs analyzein terminal.
Checklists
Rename Symbol
- [ ] rename({symbol_name: "oldName", new_name: "newName", dry_run: true}) — preview all edits
- [ ] Review graph edits (high confidence) and text_search edits (review carefully)
- [ ] If satisfied: rename({..., dry_run: false}) — apply edits
- [ ] detect_changes() — verify only expected files changed
- [ ] Run tests for affected processes
Extract Module
- [ ] context({name: target}) — see all incoming/outgoing refs
- [ ] impact({target, direction: "upstream"}) — find all external callers
- [ ] Define new module interface
- [ ] Extract code, update imports
- [ ] detect_changes() — verify affected scope
- [ ] Run tests for affected processes
Split Function/Service
- [ ] context({name: target}) — understand all callees
- [ ] Group callees by responsibility
- [ ] impact({target, direction: "upstream"}) — map callers to update
- [ ] Create new functions/services
- [ ] Update callers
- [ ] detect_changes() — verify affected scope
- [ ] Run tests for affected processes
Tools
rename — automated multi-file rename:
rename({symbol_name: "validateUser", new_name: "authenticateUser", dry_run: true})
→ 12 edits across 8 files
→ 10 graph edits (high confidence), 2 text_search edits (review)
→ Changes: [{file_path, edits: [{line, old_text, new_text, confidence}]}]
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 · 122 lines · 53 tokens per session scan A 544841cf90c9
gitnexus-refactoring is a skill published in the GitHub repository TabularisDB/tabularis (5,223 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 962 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
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…
code-review
Comprehensive code review assistant that analyzes code quality, security, and best practices.
trellis-check
Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.
readmd-code-review
Use when code blocks in a Markdown document need a security, correctness, and maintainability review.
persona-review
A format for writing short pull-request review comments, with each comment naming the location, problem, fix, and severity. A pull request is a proposed code change for review.
codex-bridge
Delegates bounded implementation work to OpenAI Codex via the codexexec MCP tool, and uses Codex as an independent reviewer or second opinion. Use when the user asks to implement, write, generate, scaffold, port, refactor, migrate, or add tests for a well-scoped code task — especially phrases like "implement X"…