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/bybren-llc/rendertrust/search-patterngit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/bybren-llc/rendertrust/search-pattern)<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/search-pattern"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/search-pattern.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.00007 | $0.01401 |
| Opus 5 | $0.00003 | $0.00700 |
| Sonnet 5 | $0.00001 | $0.00280 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
search-pattern 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 today.
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.
This is a copy
100% identical to search-pattern — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search codebase for patterns using optimized tools. Useful for refactoring, finding usage, or understanding patterns.
Usage
/search-pattern "prisma\." ts # Find direct Prisma usage in TypeScript
/search-pattern "withUserContext" # Find RLS context usage
/search-pattern "import.*icons" # Find icon imports
Search Workflow
1. Parse Arguments
- $1 = Pattern to search (required)
- $2 = File type filter (optional: ts, tsx, js, md, etc.)
2. Execute Search
Use the Grep tool with these parameters:
With file type filter (recommended for large codebases):
| Parameter | Value | Example |
|---|---|---|
pattern |
The regex pattern to find | "withUserContext" |
type |
File type to search | "ts", "tsx", "md" |
output_mode |
"files_with_matches" |
Shows matching files |
Without file type (searches all files):
| Parameter | Value | Example |
|---|---|---|
pattern |
The regex pattern to find | "prisma\." |
output_mode |
"content" |
Shows matching lines |
head_limit |
Limit results (optional) | 50 |
With context (show surrounding lines):
| Parameter | Value | Example |
|---|---|---|
pattern |
The regex pattern | "withUserContext" |
-C |
Context lines before/after | 3 |
output_mode |
"content" |
Required for context output |
3. Analyze Results
Report:
- Total matches found
- Files affected
- Common patterns noticed
- Potential refactoring opportunities
4. Categorize Findings
Group by:
- Usage patterns: How pattern is used
- Contexts: Where pattern appears
- Variations: Different uses of pattern
- Outliers: Unusual usage
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.
- today First seen · 271 lines · 7 tokens per session scan A 1a573cf3c755
search-pattern is a command published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 1,401 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to search-pattern, differing in 0 lines, and is treated as a copy.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.