Borrowing it
Nothing to install: this file belongs to irahardianto/rugged-gemini. 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/irahardianto/rugged-gemini/main/.gemini/skills/pathfinder/SKILL.mdgit clone --depth 1 https://github.com/irahardianto/rugged-geminiWrote 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/irahardianto/rugged-gemini/pathfinder)<a href="https://agentmods.dev/skills/irahardianto/rugged-gemini/pathfinder"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/pathfinder/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/irahardianto/rugged-gemini/pathfinder"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/pathfinder.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00043 | $0.03165 |
| Opus 5 | $0.00022 | $0.01582 |
| Sonnet 5 | $0.00009 | $0.00633 |
| Haiku 4.5 | $0.00004 | $0.00316 |
Grade A, and why
pathfinder 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 6d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pathfinder Skill
Session Bootstrap
Before any code exploration or analysis, confirm Pathfinder is available:
mcp({ server: "pathfinder" })
- Tools listed → Pathfinder is live. Use semantic tools for all source code operations.
- Error or empty → Pathfinder unavailable. Use built-in tools. Stop here.
Check once per session. Re-check only if a tool call fails with a connection error.
Semantic Paths
All Pathfinder tools that take a semantic_path require file_path::symbol_chain:
- ✅
src/auth.ts::AuthService.login - ✅
crates/pathfinder/src/server.rs::PathfinderServer.new - ❌
AuthService.login(interpreted as a file named "AuthService.login") - ❌
login(interpreted as a file named "login")
Bare file paths (no ::) are valid only for whole-file operations like read_source_file.
Workflows
Explore (Understand a Codebase)
1. get_repo_map(path=".", depth=5, visibility="public")
→ Full project skeleton with semantic paths
→ Low coverage_percent? Increase max_tokens
→ Files show [TRUNCATED]? Increase max_tokens_per_file
→ Use changed_since="3h" to scope to recent changes
→ Use include_extensions=["ts","tsx"] for language focus
→ Use include_tests=false to exclude test symbols
2. search_codebase(query="<entry point>", path_glob="src/**/*")
→ Find main handlers, routes, or CLI commands
→ Copy enclosing_semantic_path for next step
→ Check files_searched/files_in_scope/coverage_percent for completeness
3. read_with_deep_context(semantic_path="<entry point>")
→ Source + signatures of everything it calls
→ First call may take 5-30s during LSP warmup
4. find_callers_callees(semantic_path="<key function>", max_depth=3)
→ Who calls it (incoming) + what it calls (outgoing)
Done when: You can explain the architecture and trace a request through the system.
Impact Assessment (Before Any Change)
1. read_with_deep_context(semantic_path="<target>")
→ Current code + dependency signatures
2. find_callers_callees(semantic_path="<target>", max_depth=3)
→ All callers = blast radius
→ For large API changes: use max_depth=4-5
→ When NOT degraded: empty arrays = LSP confirmed zero
3. For each caller:
read_symbol_scope(semantic_path="<caller>")
→ Verify assumptions about the target's interface
4. get_definition(semantic_path="<suspicious dependency>")
→ Jump to external dependency source
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.
- 6d ago First seen · 308 lines · 43 tokens per session scan A d31768acd9f5
pathfinder is a skill published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 3,165 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.