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 agents/wsauret/flywheel/locator-codebasegit clone --depth 1 https://github.com/wsauret/flywheelWhat 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 | $0.00031 | $0.00185 |
| Opus 5 | $0.00015 | $0.00093 |
| Sonnet 5 | $0.00006 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
locator-codebase 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 yesterday.
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
Find WHERE files and components live. Return paths only — no analysis, no suggestions.
Search Strategy
- Glob to find candidate files by path pattern
- Grep to refine by content (function names, imports, class names)
- Categorize: implementation, tests, config, types, docs
Output Format
Files Located
path/to/file.ts- [1-line description from filename/path] (max 30 paths)
Search Patterns Used
- [Pattern]: N matches
Open Questions
- [Any ambiguities]
Max 500 words.
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.
- yesterday First seen · 30 lines · 31 tokens per session scan A b43bbfcb0075
locator-codebase is an agent published in the GitHub repository wsauret/flywheel (14 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 185 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-08-30.
Other agents, from other repositories
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…
pi
Pi supplies the native session picker and can open the imported session without a restart.
mach12:code-explorer
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.
juez-filosofia
Guardián de las seis ideas centrales y los ADRs. Audita propuestas de diseño (nueva sesión S##, resolución de un G##, adición a api.md), no diffs de código rutinarios. Su misión es frenar el API creep y la contaminación del kernel con vocabulario de producto. Lanzar desde las skills planificar-sesion y hallazgo.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.