Gograph Go Repository Intelligence
ozgurcd/gograph
Gives an agent working in a Go codebase a structural view through a local MCP server: call graphs, blast-radius and impact analysis, and bounded first-call exploration.
Get a path in the call graph from a source function to a specified destination function in the codebase.
Install Get Call Paths
$ npx skills add opensage-agent/opensage-adk --skill get-call-paths -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install opensage-agent/opensage-adk get-call-paths --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/opensage-agent/opensage-adk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/opensage/bash_tools/static_analysis/get-call-paths-to-function .claude/skills/get-call-paths && 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 "get-call-paths" agent skill from https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-call-paths-to-function into .claude/skills/get-call-paths/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-call-paths", 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/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-call-paths-to-functionType 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 opensage-agent/opensage-adk --skill get-call-paths -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install opensage-agent/opensage-adk get-call-paths --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensage-agent/opensage-adk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/opensage/bash_tools/static_analysis/get-call-paths-to-function .agents/skills/get-call-paths && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "get-call-paths" agent skill from https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-call-paths-to-function into .agents/skills/get-call-paths/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-call-paths", 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 opensage-agent/opensage-adk --skill get-call-paths -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install opensage-agent/opensage-adk get-call-paths --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensage-agent/opensage-adk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/opensage/bash_tools/static_analysis/get-call-paths-to-function .cursor/skills/get-call-paths && 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 "get-call-paths" agent skill from https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-call-paths-to-function into .cursor/skills/get-call-paths/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-call-paths", 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/opensage-agent/opensage-adk.git --path src/opensage/bash_tools/static_analysis/get-call-paths-to-function--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 opensage-agent/opensage-adk --skill get-call-paths -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install opensage-agent/opensage-adk get-call-paths --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensage-agent/opensage-adk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/opensage/bash_tools/static_analysis/get-call-paths-to-function .gemini/skills/get-call-paths && 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 "get-call-paths" agent skill from https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-call-paths-to-function into .gemini/skills/get-call-paths/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-call-paths", 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 opensage-agent/opensage-adk get-call-pathsInstalls 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 opensage-agent/opensage-adk --skill get-call-paths -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/opensage-agent/opensage-adk.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/opensage/bash_tools/static_analysis/get-call-paths-to-function .github/skills/get-call-paths && 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 "get-call-paths" agent skill from https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-call-paths-to-function into .github/skills/get-call-paths/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-call-paths", 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 opensage-agent/opensage-adk --skill get-call-paths -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install opensage-agent/opensage-adk get-call-paths --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensage-agent/opensage-adk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/opensage/bash_tools/static_analysis/get-call-paths-to-function .opencode/skills/get-call-paths && 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 "get-call-paths" agent skill from https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-call-paths-to-function into .opencode/skills/get-call-paths/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-call-paths", 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
get-call-paths- GitHub stars
- 127
- Token cost
- ~272 tokens
- SKILL.md length
- 76 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Get a path in the call graph from a source function to a specified destination function in the codebase.
- Tasks that involve Codebase onboarding
- SKILL.md covers Usage, Parameters, Return Value and Requires Sandbox
- Runs Python scripts from its folder; calls python3
- Tasks that involve Static analysis and SAST
What it does
Get Call Paths is an agent skill from opensage-agent/opensage-adk. Get a path in the call graph from a source function to a specified destination function in the codebase. It's very useful when you want to find call paths to a function.
Its SKILL.md is about 270 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/get_call_paths_to_function.py`).
It sits in Development, covering Codebase onboarding and Static analysis and SAST. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Codebase onboarding
- Tasks that involve Static analysis and SAST
Example prompts
- “/get-call-paths”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 54d6470. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Get Call Paths loads about 272 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 76 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); the scripts in this folder are not scanned.
SKILL.md
The full file from opensage-agent/opensage-adk at commit 54d6470, republished under its Apache-2.0 licence (© opensage-agent). 76 words, ~272 tokens.
Download SKILL.mdSave it as
.claude/skills/get-call-paths/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- get-call-paths
- description
- Get a path in the call graph from a source function to a specified destination function in the codebase. It's very useful when you want to find call paths to a function.
- should_run_in_sandbox
- main
- returns_json
- false
Get Call Paths Tool
Get a path in the call graph from a source function to a specified destination function in the codebase.
Usage
python3 /bash_tools/static_analysis/get-call-paths-to-function/scripts/get_call_paths_to_function.py "DST_FUNCTION" \
--dst-file "path/to/dst_file" \
--src-function "SRC_FUNCTION" \
--src-file "path/to/src_file"Parameters
dst_function_name(positional): Destination function name.--dst-file: File path where the destination function is defined (optional).--src-function: Source function name (optional; defaultLLVMFuzzerTestOneInput).--src-file: File path where the source function is defined (optional).
Return Value
Returns JSON text with a top-level key result containing call path info.
Requires Sandbox
neo4j, codeql, joern
© opensage-agent, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in src/opensage/bash_tools/static_analysis/get-call-paths-to-function of opensage-agent/opensage-adk.
- SKILL.md
- scripts/get_call_paths_to_function.py
Open the folder on GitHubat commit 54d6470
Compare with similar skills
Get Call Paths 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 |
|---|---|---|---|---|---|---|
| Get Call Paths this skillopensage-agent/opensage-adk | 127 | — | ~272 | Automated safety check: Pass | Apache-2.0 | |
| Gograph Go Repository Intelligenceozgurcd/gograph | 227 | — | ~4.8k | Automated safety check: Notes | MIT | |
| Ripwire Graph Queryredhat-et/ripwire | 2.4k | — | ~1.1k | Automated safety check: Notes | Apache-2.0 | |
| Code Graph Mermaid Diagramstrailofbits/skills | 7.4k | 1 repos | ~1.7k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| New Rule for sonar-javaSonarSource/sonar-java | 1.2k | — | ~833 | Automated safety check: Pass | Custom licence | |
| Golang Continuous Integrationsamber/cc-skills-golang | 3.4k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Ripwire Graph Query
redhat-et/ripwire
Answers call-graph questions that combine several conditions, such as complex functions that reach a target or untested symbols near main, using ripwire's graph-query mode.
- Official
Code Graph Mermaid Diagrams
trailofbits/skills
Generates Mermaid diagrams from Trailmark code graphs, including call graphs, class hierarchies, module dependency maps, complexity heatmaps and attack surface data flows.
- Official
New Rule for sonar-java
SonarSource/sonar-java
Sets the sonar-java conventions for adding an analyzer rule: metadata from rule-api, test locations, MethodMatchers and what not to commit or change.
Golang Continuous Integration
samber/cc-skills-golang
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release…
Arandu Doctor Findings
arandu-io/arandu
Explains what each aru doctor architecture-check finding means in the Arandu Go framework, why it is never suppressed, and how to fix the line it points to.
More from opensage-agent/opensage-adk
All 21 skills in this repoRun Fuzzing Campaign
opensage-agent/opensage-adk
Run a fuzzing campaign using AFL++ with optional seeds; supports --custommutatorpath (you can write your own custom mutator and use this to execute).
Pool
opensage-agent/opensage-adk
Run N tasks under a concurrency cap K via a sliding-window worker pool.
Create New Tool
opensage-agent/opensage-adk
Scaffold a new bashtools Skill under bashtools/newtools/. An agent skill from opensage-agent/opensage-adk.
Extract Crashes
opensage-agent/opensage-adk
Extract crash inputs from fuzzing output into a target directory.
Get Callee
opensage-agent/opensage-adk
Tool to get the callee of a function in the codebase by function name and file path.
Get Caller
opensage-agent/opensage-adk
Tool to get the caller of a function in the codebase. An agent skill from opensage-agent/opensage-adk.
Related
Categories
Questions about Get Call Paths
What does Get Call Paths do?
Get a path in the call graph from a source function to a specified destination function in the codebase. Get Call Paths is an agent skill from opensage-agent/opensage-adk. Get a path in the call graph from a source function to a specified destination function in the codebase.
When should I use Get Call Paths?
Get Call Paths fits situations like: tasks that involve Codebase onboarding; tasks that involve Static analysis and SAST.
How do I install Get Call Paths in Claude Code?
Run `npx skills add opensage-agent/opensage-adk --skill get-call-paths -a claude-code`. Or copy the skill folder (src/opensage/bash_tools/static_analysis/get-call-paths-to-function in opensage-agent/opensage-adk) into .claude/skills/get-call-paths in your project. Claude Code loads it when a task matches its description.
How do I install Get Call Paths in Codex?
Run `npx skills add opensage-agent/opensage-adk --skill get-call-paths -a codex`. Or copy the skill folder (src/opensage/bash_tools/static_analysis/get-call-paths-to-function in opensage-agent/opensage-adk) into .agents/skills/get-call-paths in your project. Codex loads it when a task matches its description.
Can I use Get Call Paths 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 opensage-agent/opensage-adk --skill get-call-paths -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/get-call-paths, .gemini/skills/get-call-paths, .github/skills/get-call-paths and .opencode/skills/get-call-paths in your project.
What does Get Call Paths need to run?
Going by SKILL.md and its folder, Get Call Paths needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Get Call Paths access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Get Call Paths 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Get Call Paths use?
Get Call Paths is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Get Call Paths use?
About 272 tokens (SKILL.md is roughly 1.1k 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 Get Call Paths?
Skills that share tags, products or a category with Get Call Paths: Gograph Go Repository Intelligence (ozgurcd/gograph, 227 stars), Ripwire Graph Query (redhat-et/ripwire, 2.4k stars), Code Graph Mermaid Diagrams (trailofbits/skills, 7.4k stars) and New Rule for sonar-java (SonarSource/sonar-java, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Get Call Paths?
opensage-agent (a GitHub organization) maintains it in opensage-agent/opensage-adk, which has 127 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on August 4, 2026.
Source: opensage-agent/opensage-adk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.