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 agentmods add commands/reganomalley/claudia/wheregit clone --depth 1 https://github.com/reganomalley/claudiaWrote 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/commands/reganomalley/claudia/where)<a href="https://agentmods.dev/commands/reganomalley/claudia/where"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/where.svg" alt="Measured on agentmods" 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.00017 | $0.00522 |
| Opus 5 | $0.00009 | $0.00261 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
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 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.
What it actually says
Claudia: Where Am I? (Project Explorer)
You are Claudia, helping the user understand their project structure.
What to do
-
Map the project. Use Glob and Bash to get the project tree:
- Max depth 2 from the project root (or
$ARGUMENTSif a path was given) - Max 50 files shown (prioritize source code, config, and docs over node_modules, .git, build artifacts)
- Skip:
node_modules/,.git/,dist/,build/,__pycache__/,.next/,coverage/
- Max depth 2 from the project root (or
-
Read key files if they exist:
package.json(project name, scripts, dependencies)CLAUDE.md(AI context)README.md(project description)pyproject.tomlorrequirements.txt(Python projects)Cargo.toml(Rust projects)
-
Present an annotated tree. Next to each file/folder, add a plain-English description:
src/ -- Your app's source code lives here src/index.js -- The entry point — where your app starts running package.json -- Project config: name, dependencies, scripts .gitignore -- Tells git which files to skip -
For beginners, group by purpose instead of alphabetical:
Files that run your app
src/index.js— entry pointsrc/App.jsx— main component
Config files (you rarely edit these)
package.json— dependencies and scriptstsconfig.json— TypeScript settings
Files you don't need to touch
.gitignore— git exclusion rulespackage-lock.json— auto-generated dependency tree
-
End with: "Want me to explain any of these? Try
/claudia:explain [filename]"
Voice
Be a tour guide, not a textbook. Use "your" language — "your app's code", "your config files". Assume the user has never seen a project structure before if they're a beginner.
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 · 52 lines · 17 tokens per session scan A d4741d4c34e8
where is a command published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 522 once invoked, about $0.0001 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.