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 emaraschio/cursor-commands --skill pathfindergit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/emaraschio/cursor-commands/pathfinder)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/pathfinder"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/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/emaraschio/cursor-commands/pathfinder"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/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.00110 | $0.01388 |
| Opus 5 | $0.00055 | $0.00694 |
| Sonnet 5 | $0.00022 | $0.00278 |
| Haiku 4.5 | $0.00011 | $0.00139 |
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pathfinder
Role
You act as a senior project planner. The user gives a project goal and whatever context they have; you return a fog map that separates what is already settled from what is still unknown, and turns each unknown into a concrete next move. This skill is plan-only: it maps the terrain, it does not build the project in the same turn.
When to use
Use before a greenfield project, a messy or under-specified request, or any workflow where the next step feels obvious but is undercooked. The point is to map the fog of war first (the decisions, research gaps, and unknowns that could derail the work later) so building starts on solid ground. For a six-part agent delegation contract, use define-agent-goal. For a runnable prompt, use structure-prompt.
Workflow
Run phases in order. Do not deliver the map until Phase 3. Do not execute the project, scaffold code, or run destructive commands when delivering the map unless the user explicitly says to skip planning and build now.
Phase 0: Intake
- Extract the project goal (the outcome the user wants) and the known context (requirements, constraints, stakeholders, links, notes) from the message.
- If the goal is missing, ask one focused question before proceeding.
- Produce a one-sentence restatement of what the project is trying to achieve.
Phase 1: Discovery
Ask structured clarifying questions (use AskQuestion when available) to separate what is fixed from what is unknown. Cover only gaps the context leaves open:
- What is genuinely non-negotiable versus assumed?
- Which choices are still open and materially shape the project?
- What unknowns could change the whole plan if the answer surprises you?
- Who owns the decisions, and what is the deadline or budget pressure?
Aim for 4 to 6 high-signal questions. Skip anything the user already answered.
Phase 2: Draft the map
Fill the map template below. Keep it to about one page: prefer tables and bullets over prose. While drafting:
What ships with it
3 files 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.
- 6d ago First seen · 108 lines · 110 tokens per session scan A 2f6c5b13fc5a
pathfinder is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 1,388 once invoked, about $0.0006 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
grok-build-supervisor
Initialize the persistent local proxy, then immediately ensure a visible Grok Build TUI for the current workspace when /grokexecute on activates, and continuously supervise that coding-agent session through a user-level Supervisor daemon as the user sends work, waits for completion, reconnects from another host task…
cursor-delegate
Delegate bounded light-to-medium implementation, investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns direction and risk boundaries. Also use when the user explicitly asks to create, keep, continue, inspect, or close the same Cursor execution session…
grok-executor-mode
Explicit Grok executor on/off control and task-local execution policy. Accept a direct user invocation with exactly on or off; never infer activation from ordinary requests, quoted examples, or partial matches.
cce-routing
Use Cursor Bridge's read-only cursorcontextengine for unfamiliar project understanding when the exact code location is unknown or the task requires tracing behavior, symbols, callers and callees, data flow, registrations, interface implementations, ownership boundaries, or cross-module relationships. Trigger for…
grok-executor-off
Explicitly disable Grok executor mode for this task without cancelling work or closing its terminal. Select this skill directly; no argument is required.
grok-executor-on
Explicitly enable Grok executor mode for this task and prepare its visible terminal. Select this skill directly; no argument is required.