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.
git clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/a-safe-pulse/search-pattern)<a href="https://agentmods.dev/commands/bybren-llc/a-safe-pulse/search-pattern"><img src="https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/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.1 | $0.00007 | $0.01398 |
| Opus 5 | $0.00003 | $0.00699 |
| 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 2d 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.
This is a copy
94% identical to search-pattern — 12 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 "pool\.query" ts # Find direct database queries 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 | "pool\.query" |
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.
- 2d ago First seen · 271 lines · 7 tokens per session scan A fa564f1b488b
search-pattern is a command published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 1,398 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to search-pattern, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.