where

A command that locates saved work in a Founder OS project and explains which project or folder it belongs to.

In plain words
What is it for?
Use it to find a project or document by describing what you remember about it. It can then open the folder for you.
Why use it?
It removes the need to search through folders manually when work seems to have disappeared. It also reports when a matching folder is not backed up.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/arcassystems/founderos/where
Clone the repo
git clone --depth 1 https://github.com/ARCASSystems/FounderOS

Made for: Claude Code.

Per session 85 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 251 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00085 $0.00251
Opus 5 $0.00043 $0.00125
Sonnet 5 $0.00017 $0.00050
Haiku 4.5 $0.00009 $0.00025

Measured 2d ago against content hash 815def55e34c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

where 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 2d 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.

.claude/commands/where.md · 13 lines

What it actually says

Run the where skill.

Looking for: $ARGUMENTS

Run python scripts/where.py --days 14 $ARGUMENTS first (the words they gave you surface matching folders first), then answer in two or three plain sentences leading with the work, not the location. Widen the window if nothing looks familiar. If any folder comes back NOT BACKED UP, say so even though they did not ask - that is the more urgent finding. Close by offering to open the folder; on a yes, open it with python scripts/open_folder.py "<folder>", never with a raw explorer / open / xdg-open command.

Never explain the folder architecture to someone who has just told you they cannot find their work.

Changes

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.

  1. 2d ago First seen · 13 lines · 85 tokens per session scan A 815def55e34c

Subscribe to this mod's changes

where is a command published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 18d ago), licensed MIT. It adds 85 tokens to every session and 251 once invoked, about $0.0004 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-08-31.