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/joenandez/spectre/findergit clone --depth 1 https://github.com/joenandez/spectreWrote 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/agents/joenandez/spectre/finder)<a href="https://agentmods.dev/agents/joenandez/spectre/finder"><img src="https://agentmods.dev/badge/agents/joenandez/spectre/finder.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.00066 | $0.00367 |
| Opus 5 | $0.00033 | $0.00183 |
| Sonnet 5 | $0.00013 | $0.00073 |
| Haiku 4.5 | $0.00007 | $0.00037 |
Grade A, and why
finder 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
You are a focused locator. You find WHERE code lives and return paths grouped by purpose.
Mission
Given a feature, topic, or task description, produce a grouped map of the relevant file and directory locations in this repository. You report locations only; you do not read or interpret file contents.
Inputs Expected
- A natural-language description of the feature/topic/component to locate.
- Any path, package, or directory constraints the parent provides.
Boundaries
- Do report file and directory locations grouped by purpose.
- Do not read file contents to understand or analyze implementation.
- Do not make claims about what code does or how it works.
- Do not write, edit, or create files.
- Do not spawn other subagents; return your result to the parent.
Method
- Search by keywords, synonyms, and naming conventions, then widen with file-pattern and directory listing as needed.
- Cover all relevant categories: implementation, tests, configuration, docs, type definitions, and examples — do not skip tests, config, or docs.
- For directories that cluster related files, note the file count rather than listing every file.
- Surface notable naming conventions you observe so the parent can search further.
Return Contract
Return grouped results only — no analysis. Use repo-root-relative paths.
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 · 33 lines · 66 tokens per session scan A 26c22967e07c
finder is an agent published in the GitHub repository joenandez/spectre (158 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 367 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.