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 skills add pilinux/gorest --skill code-navigationgit clone --depth 1 https://github.com/pilinux/gorestWrote 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/pilinux/gorest/code-navigation)<a href="https://agentmods.dev/skills/pilinux/gorest/code-navigation"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/code-navigation/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/pilinux/gorest/code-navigation"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/code-navigation.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.00020 | $0.00326 |
| Opus 5.5 | $0.00008 | $0.00130 |
| Sonnet 5.5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
code-navigation 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.
What it actually says
Code Navigation
When to Use
- You need the authoritative locations and immediate impact surface for a symbol, endpoint, or config key before making changes.
Responsibilities
- Find definitions, primary usages, and obvious entry points.
- Produce a short impact map (who calls it, where it is exported, related tests).
- Keep reads minimal (prefer 1-5 files).
Rules
- Read-only; do not modify files or run shell commands.
- Use
grepfirst, then targetedreadfor the top matches. - Provide
path:linecitations for all claims.
Workflow
- Clarify the exact symbol or endpoint.
- Narrow candidates via glob and grep.
- Read 1-3 highest-confidence files.
- Report: primary locations, secondary references, change impact.
Output
- Locations:
path:lineentries. - Impact: 1-3 bullets describing callers, dependents, and test coverage.
- Next: suggested file to open if deeper context is required.
Examples
- "Where is JWT issued and validated?" - definition + callers + tests.
- "Which packages import
database.GetDB()?" - list of usages.
Related Skills
source-search(broad grep),file-reader(detailed read),ast-introspection(structure-aware)
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 · 49 lines · 20 tokens per session scan A a77434b75b24
code-navigation is a skill published in the GitHub repository pilinux/gorest (506 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 326 once invoked, about $0.0001 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
evm-rpc
Query EVM JSON-RPC methods for transaction debugging and endpoint triage, including ethgetTransactionReceipt and debugtraceTransaction. Use when the user asks to inspect tx status, retrieve receipts, run tracers, compare EVM vs Cosmos outcomes, or choose between EVM RPC and Comet RPC endpoints.
nibid-gov-upgrade
Queries Nibiru governance proposals (including software-upgrade proposals) using the nibid CLI, maps explorer UI fields to on-chain queries, computes quorum/threshold/veto metrics, and correlates validator votes using staking queries. Use when the user mentions nibid q gov, governance proposals, software upgrades…
nibiru-gql
Query the Nibiru Heart Monitor GraphQL API and its indexed chain data. Use for wallet balances, staking, validators, delegations, Cosmos transaction messages, Wasm events, indexing gaps, or comparisons with Sai Keeper. Read the matching reference before querying.
sai-perps
Query and reconcile Sai Perps data from live contracts, Sai Keeper GraphQL and Postgres, and DexPal REST. Use for markets, trades, fees, open interest, vaults, balances, referrals, or disagreements between on-chain and indexed data. Use agent skill sai-ops for mutations.
golang
Use when building Go backend services, implementing goroutines/channels, handling errors idiomatically, writing tests with testify, or following Go best practices for APIs/CLI tools.
nibiru-cli-nibid
Query Nibiru chain state and submit transactions with the nibid CLI, including setup via ud, config inspection, key discovery with nibid keys list, bank transfers, bank balance queries, EVM multi-VM balance checks such as nibid q evm balance for Sai USDC, wasm contract queries, wasm execute/instantiate flows, and…