Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.
Install Gitnexus Exploring
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-exploring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-exploring .claude/skills/gitnexus-exploring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gitnexus-exploring" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-exploring into .claude/skills/gitnexus-exploring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-exploring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-exploringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-exploring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-exploring .agents/skills/gitnexus-exploring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gitnexus-exploring" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-exploring into .agents/skills/gitnexus-exploring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-exploring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-exploring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-exploring .cursor/skills/gitnexus-exploring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gitnexus-exploring" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-exploring into .cursor/skills/gitnexus-exploring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-exploring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws-samples/sample-kolya-br-proxy.git --path .claude/skills/gitnexus/gitnexus-exploring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-exploring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-exploring .gemini/skills/gitnexus-exploring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gitnexus-exploring" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-exploring into .gemini/skills/gitnexus-exploring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-exploring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-exploringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-exploring .github/skills/gitnexus-exploring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gitnexus-exploring" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-exploring into .github/skills/gitnexus-exploring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-exploring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-exploring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-exploring .opencode/skills/gitnexus-exploring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gitnexus-exploring" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-exploring into .opencode/skills/gitnexus-exploring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-exploring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gitnexus-exploring- GitHub stars
- 106
- Used in
- 11 other repos
- Token cost
- ~749 tokens
- SKILL.md length
- 101 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT-0
At a glance
A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.
- The user asks how code works
- SKILL.md covers When to Use, Workflow, Checklist and Resources, plus 2 more sections
- Calls npx
- Wants to understand architecture
What it does
Gitnexus Exploring is an agent skill from aws-samples/sample-kolya-br-proxy, published by the product's own GitHub organization. Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Authentication. The licence is MIT-0.
When your agent uses it
- The user asks how code works
- Wants to understand architecture
- Trace execution flows
- Explore unfamiliar parts of the codebase
Example prompts
- “How does X work?”
- “What calls this function?”
- “Show me the auth flow”
- “/gitnexus-exploring”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 9c3dcee. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Gitnexus Exploring loads about 749 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 101 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws-samples/sample-kolya-br-proxy at commit 9c3dcee, republished under its MIT-0 licence (© aws-samples). 101 words, ~749 tokens.
Download SKILL.mdSave it as
.claude/skills/gitnexus-exploring/SKILL.md (or your agent's skills folder).- name
- gitnexus-exploring
- description
- Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
Exploring Codebases with GitNexus
When to Use
- "How does authentication work?"
- "What's the project structure?"
- "Show me the main components"
- "Where is the database logic?"
- Understanding code you haven't seen before
Workflow
1. READ gitnexus://repos → Discover indexed repos
2. READ gitnexus://repo/{name}/context → Codebase overview, check staleness
3. gitnexus_query({query: "<what you want to understand>"}) → Find related execution flows
4. gitnexus_context({name: "<symbol>"}) → Deep dive on specific symbol
5. READ gitnexus://repo/{name}/process/{name} → Trace full execution flowIf step 2 says "Index is stale" → run
npx gitnexus analyzein terminal.
Checklist
- [ ] READ gitnexus://repo/{name}/context
- [ ] gitnexus_query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] gitnexus_context on key symbols for callers/callees
- [ ] READ process resource for full execution traces
- [ ] Read source files for implementation detailsResources
| Resource | What you get |
|---|---|
gitnexus://repo/{name}/context | Stats, staleness warning (~150 tokens) |
gitnexus://repo/{name}/clusters | All functional areas with cohesion scores (~300 tokens) |
gitnexus://repo/{name}/cluster/{name} | Area members with file paths (~500 tokens) |
gitnexus://repo/{name}/process/{name} | Step-by-step execution trace (~200 tokens) |
Tools
gitnexus_query — find execution flows related to a concept:
gitnexus_query({query: "payment processing"})
→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
→ Symbols grouped by flow with file locationsgitnexus_context — 360-degree view of a symbol:
gitnexus_context({name: "validateUser"})
→ Incoming calls: loginHandler, apiMiddleware
→ Outgoing calls: checkToken, getUserById
→ Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)Example: "How does payment processing work?"
1. READ gitnexus://repo/my-app/context → 918 symbols, 45 processes
2. gitnexus_query({query: "payment processing"})
→ CheckoutFlow: processPayment → validateCard → chargeStripe
→ RefundFlow: initiateRefund → calculateRefund → processRefund
3. gitnexus_context({name: "processPayment"})
→ Incoming: checkoutHandler, webhookHandler
→ Outgoing: validateCard, chargeStripe, saveTransaction
4. Read src/payments/processor.ts for implementation details© aws-samples, MIT-0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/gitnexus/gitnexus-exploring of aws-samples/sample-kolya-br-proxy.
Open the folder on GitHubat commit 9c3dcee
Used in 12 other repositories
We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 11 other GitHub owners. This page covers the copy in aws-samples/sample-kolya-br-proxy, which our catalogue first saw on October 7, 2026.
- ML4ITS/TimeVQVAE.agents/skills/gitnexus/exploring
- kunwarVivek/mcp-github-project-manager.agents/skills/gitnexus-exploring
- Arenukvern/mcp_flutter.claude/skills/gitnexus/gitnexus-exploring
- BA-CalderonMorales/terminal-jarvis.agents/skills/gitnexus/gitnexus-exploring
- ceilf6/FrontAgent.agents/skills/gitnexus/gitnexus-exploring.claude/skills/gitnexus/gitnexus-exploring
- Sayhi-bzb/CharDesk.agents/skills/gitnexus/gitnexus-exploring
- mindfold-ai/Trellis.claude/skills/gitnexus/gitnexus-exploring
- TabularisDB/tabularis.claude/skills/gitnexus/gitnexus-exploring
- ucsandman/DashClaw.agents/skills/gitnexus-exploring.claude/skills/gitnexus-exploring
- Apra-Labs/apra-fleet.claude/skills/gitnexus/gitnexus-exploring
- Sayhi-bzb/Agent-HTML.claude/skills/gitnexus/gitnexus-exploring
- NeverSight/learn-skills.devdata/skills-md/abhigyanpatwari/gitnexus/gitnexus-exploring
Compare with similar skills
Gitnexus Exploring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gitnexus Exploring this skillaws-samples/sample-kolya-br-proxy | 106 | 11 repos | ~749 | Automated safety check: Pass | MIT-0 | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Supabase Development and Debuggingsupabase/agent-skills | 2.7k | 3 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Better Auth Best Practiceslatitude-dev/latitude-llm | 4.7k | 7 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Supabasecurvenote/curvenote | 169 | 5 repos | ~2.2k | Automated safety check: Pass | Custom licence | |
| Gemini Live API Devgoogle-gemini/gemini-skills | 4.3k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Supabase Development and Debugging
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
Better Auth Best Practices
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
Supabase
curvenote/curvenote
A skill your agent uses when doing ANY task involving Supabase.
- Official
Gemini Live API Dev
google-gemini/gemini-skills
A skill your agent uses when building real-time, bidirectional streaming applications with the Gemini Live API, or migrating legacy Live models (2.0/2.5/3.1) to Gemini 3.8 Live.
Agentic Wallet
coinbase/agentic-wallet-skills
Crypto wallet operations via the awal CLI — sign in, check balances, send USDC/ETH/POL/SOL, trade tokens, fund the wallet, and use the x402 payment protocol to discover paid services, pay for API…
More from aws-samples/sample-kolya-br-proxy
- Official
Gitnexus Debugging
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user is debugging a bug, tracing an error, or asking why something fails.
- Official
Gitnexus Impact Analysis
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user wants to know what will break if they change something, or needs safety analysis before editing code.
- Official
Gitnexus Refactoring
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user wants to rename, extract, split, move, or restructure code safely.
- Official
Gitnexus CLI
aws-samples/sample-kolya-br-proxy
A skill your agent uses 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.
- Official
Gitnexus Guide
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference.
Related
Categories
Questions about Gitnexus Exploring
What does Gitnexus Exploring do?
A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Gitnexus Exploring is an agent skill from aws-samples/sample-kolya-br-proxy, published by the product's own GitHub organization. Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.
When should I use Gitnexus Exploring?
Gitnexus Exploring fits situations like: the user asks how code works; wants to understand architecture; trace execution flows; explore unfamiliar parts of the codebase.
How do I install Gitnexus Exploring in Claude Code?
Run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a claude-code`. Or copy the skill folder (.claude/skills/gitnexus/gitnexus-exploring in aws-samples/sample-kolya-br-proxy) into .claude/skills/gitnexus-exploring in your project. Claude Code loads it when a task matches its description.
How do I install Gitnexus Exploring in Codex?
Run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a codex`. Or copy the skill folder (.claude/skills/gitnexus/gitnexus-exploring in aws-samples/sample-kolya-br-proxy) into .agents/skills/gitnexus-exploring in your project. Codex loads it when a task matches its description.
Can I use Gitnexus Exploring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-exploring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitnexus-exploring, .gemini/skills/gitnexus-exploring, .github/skills/gitnexus-exploring and .opencode/skills/gitnexus-exploring in your project.
What does Gitnexus Exploring need to run?
Going by SKILL.md and its folder, Gitnexus Exploring needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Gitnexus Exploring access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Gitnexus Exploring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gitnexus Exploring use?
Gitnexus Exploring is published under the MIT-0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gitnexus Exploring use?
About 749 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gitnexus Exploring?
Skills that share tags, products or a category with Gitnexus Exploring: Fortify Development (coollabsio/coolify, 63k stars), Supabase Development and Debugging (supabase/agent-skills, 2.7k stars), Better Auth Best Practices (latitude-dev/latitude-llm, 4.7k stars) and Supabase (curvenote/curvenote, 169 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gitnexus Exploring?
aws-samples (a GitHub organization, an official publisher) maintains it in aws-samples/sample-kolya-br-proxy, which has 106 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.
Source: aws-samples/sample-kolya-br-proxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.