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/coralogix/canopy/find-examplesgit clone --depth 1 https://github.com/coralogix/canopyWrote 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/coralogix/canopy/find-examples)<a href="https://agentmods.dev/commands/coralogix/canopy/find-examples"><img src="https://agentmods.dev/badge/commands/coralogix/canopy/find-examples.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 | $0.00000 | $0.00368 |
| Opus 5 | $0.00000 | $0.00184 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
find-examples 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 4d 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
/find-examples
Find usage examples for a function, class, pattern, or concept in the codebase.
Trigger
Use when the developer asks: "Show me examples of X", "How is Y used?", "Where is Z called?"
Steps
- Parse the developer's message to identify what to search for: a function name, class name, pattern, or concept.
- Search for it across the codebase using text search. Look for:
- Direct calls:
foo(,foo.bar(,new Foo( - Imports:
from x import foo,import foo,require('foo') - Type annotations:
: Foo,-> Foo
- Direct calls:
- Find 3-5 representative examples from different parts of the codebase (not 5 examples from the same file).
- For each example, show the relevant code snippet with 3-5 lines of context.
- After the examples, briefly explain the common usage pattern you observed.
Output Format
Found N usages of `[name]`. Here are representative examples:
**Example 1** — `path/to/file.py:42`
```[language]
[code snippet with context]
[1-line explanation of what's notable about this usage]
Example 2 — ...
Common pattern: [2-3 sentence summary of how this is typically used]
## Rules
- Always show the file path and line number
- If there are more than 10 usages, show the most diverse 3-5 (different callers, different patterns)
- If there are fewer than 3 usages, show all of them and note "this is used sparingly"
- If nothing is found, say so clearly and suggest alternative search terms
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.
- 4d ago First seen · 43 lines · 0 tokens per session scan A f608149bf2f7
find-examples is a command published in the GitHub repository coralogix/canopy (89 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 368 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.