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 skills/syngnat/gonavi/skillnpx skills add Syngnat/GoNavi --skill skillgit clone --depth 1 https://github.com/Syngnat/GoNaviWrote 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/syngnat/gonavi/skill)<a href="https://agentmods.dev/skills/syngnat/gonavi/skill"><img src="https://agentmods.dev/badge/skills/syngnat/gonavi/skill.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.00144 | $0.03181 |
| Opus 5 | $0.00072 | $0.01590 |
| Sonnet 5 | $0.00029 | $0.00636 |
| Haiku 4.5 | $0.00014 | $0.00318 |
Grade A, and why
gonavi-cli 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 4d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoNavi CLI
The GoNavi CLI is a standalone, headless binary for the GoNavi database client (Wails app). It queries and manages saved connections without the GUI and is built for scripting and AI agents: stdout carries machine-readable data (JSON/JSONL/CSV/Markdown), stderr carries JSON error reports, and every invocation exits with a stable exit code.
Install
Download the matching gonavi-cli_${VERSION}_${goos}_${arch} archive and
gonavi-cli_${VERSION}_checksums.txt file from a GoNavi GitHub Release, verify
the SHA256 checksum, extract the archive, then run:
gonavi version # -> {"version":"0.9.3"}
- The CLI is currently distributed through verified GitHub Release archives, not npm.
GONAVI_CLI_RELEASE_BASE_URLmay point at a mirror that preserves the same release asset names and checksum file. Release assets are namedgonavi-cli_${VERSION}_${goos}_${arch}.tar.gz(darwin/linux) or.zip(win32), plusgonavi-cli_${VERSION}_checksums.txt.
Data root and environment
- Saved connections and the SQL audit log live under the GoNavi data root:
GONAVI_DATA_ROOTif set, otherwise~/.gonavi. --data-root PATH(before the command) overrides it for one invocation:gonavi --data-root /srv/gonavi-data list-connections.- Never put secrets in argv — they show up in process listings. Pass them via environment variables (see Connection management) or a connection file.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (bad flags, missing args, invalid format) |
| 3 | Connection error (not found, ambiguous, save/import failed, invalid file) |
| 4 | Policy denied (write attempted without --allow-write, or read-only connection) |
| 5 | Execution failure (SQL error, output failure, invalid result shape) |
| 6 | Cancelled (interrupt, timeout, explicit cancellation) |
| 7 | Outcome unknown (execution result could not be determined) |
Error contract
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 265 lines · 144 tokens per session scan A 142663074180
gonavi-cli is a skill published in the GitHub repository Syngnat/GoNavi (1,887 stars, last pushed 2d ago), licensed Apache-2.0. It adds 144 tokens to every session and 3,181 once invoked, about $0.0007 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
tabularis-plugin-driver
Use when creating or updating a Tabularis database driver plugin in Rust. Covers modern manifest fields, JSON-RPC over stdio, modular plugin layout, MySQL-level feature coverage targets, optional UI extensions, and validation against Tabularis repo rules.
gitnexus-guide
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?".
tabularis-pr-review
Use when reviewing a Tabularis pull request locally — checking code quality against the repo's own rules, verifying the PR's claims, running its tests on the correct branch, and preparing real test data plus a manual test plan for the human. Use when the user says 'review PR #N', 'lass uns PR reviewen', 'check this…
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".