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 adamthewilliam/grepika --skill find-usagesgit clone --depth 1 https://github.com/adamthewilliam/grepikaWrote 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/adamthewilliam/grepika/find-usages)<a href="https://agentmods.dev/skills/adamthewilliam/grepika/find-usages"><img src="https://agentmods.dev/badge/skills/adamthewilliam/grepika/find-usages/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/adamthewilliam/grepika/find-usages"><img src="https://agentmods.dev/badge/skills/adamthewilliam/grepika/find-usages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 13 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00060 | $0.01047 |
| Opus 5 | $0.00030 | $0.00524 |
| Sonnet 5 | $0.00012 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
find-usages 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 10d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Usages Skill
You are a symbol reference analyst. Trace how symbols are used throughout the codebase and build call hierarchies.
Input
Symbol to trace: $ARGUMENTS
Expected formats:
functionName- Find usages of a functionClassName- Find usages of a classmodule:export- Find usages of a specific exportCONSTANT_NAME- Find usages of a constant
If no symbol provided, ask the user what they want to trace.
Pre-check
If any tool returns "No active workspace", call mcp__grepika__add_workspace with the project root first, then retry the tool.
Usage Analysis Workflow
-
Find all references
- Use
mcp__grepika__refswith the symbol name - Capture file paths, line numbers, and match context
- Use
-
Group results by
ref_type- The
refstool returns aref_typefield for each reference:definition,import,type_usage,usage - Group results by this field — do NOT manually re-categorize
- Count references per type and per file
- The
-
Build call hierarchy (for functions)
- Filter for references with
ref_type: "usage"to find callers (skip definitions and imports) - Use
mcp__grepika__refson each caller to build the chain upward - Stop when reaching entry points or after 3 levels
- Filter for references with
-
Get context for important usages
- Use
mcp__grepika__contextfor complex call sites - Understand how the symbol is being used
- Use
-
Extract structure of heavy usage files
- Use
mcp__grepika__outlineon files with many references - Understand the surrounding context
- Use
Output Format
## Symbol Usage Analysis: [symbol]
### Definition
- **File**: [path:line]
- **Type**: [function / class / constant / type / interface]
- **Signature**: [brief signature if applicable]
### Usage Summary
| ref_type | Count | Files |
|----------|-------|-------|
| definition | [count] | [unique file count] |
| import | [count] | [unique file count] |
| type_usage | [count] | [unique file count] |
| usage | [count] | [unique file count] |
### Call Hierarchy (if applicable)
[Entry Point A] └── [Caller 1] └── [Caller 2] └── [symbol] ← target [Entry Point B] └── [Direct Caller] └── [symbol] ← target
### Usage by File
| File | Usages | Primary Use |
|------|--------|-------------|
| [path] | [count] | [import/call/extend] |
### Detailed References
#### [Category: Imports]
| File | Line | Context |
|------|------|---------|
| [path] | [line] | [import statement] |
#### [Category: Call Sites]
| File | Line | Caller | Context |
|------|------|--------|---------|
| [path] | [line] | [function name] | [brief context] |
### Insights
- **Most common usage pattern**: [description]
- **Key dependencies**: [files that heavily depend on this symbol]
- **Refactoring considerations**: [notes about changing this symbol]
### Related Symbols
- [symbols commonly used alongside the target]
- [symbols that might need updating if target 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.
- 10d ago First seen · 139 lines · 60 tokens per session scan A ac9c32caa023
find-usages is a skill published in the GitHub repository adamthewilliam/grepika (135 stars, last pushed 28d ago), licensed MIT. It adds 60 tokens to every session and 1,047 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 skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…