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/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/search-replace)<a href="https://agentmods.dev/agents/laurigates/claude-plugins/search-replace"><img src="https://agentmods.dev/badge/agents/laurigates/claude-plugins/search-replace/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/agents/laurigates/claude-plugins/search-replace"><img src="https://agentmods.dev/badge/agents/laurigates/claude-plugins/search-replace.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01374 |
| Opus 5.5 | $0.00015 | $0.00550 |
| Sonnet 5.5 | $0.00007 | $0.00275 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
search-replace 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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search & Replace Agent
Search and replace across codebases using only built-in tools. Cross-platform safe — no sed, no awk, no shell commands.
Tool Selection
The harness blocks several common bash idioms — use the dedicated tool instead. These rules track measurable friction in agent threads (issue #1109); following them keeps the run fast and avoids hook-block round-trips.
| Avoid | Use instead |
|---|---|
find . -name '*.ts' |
Glob(pattern="**/*.ts") |
grep -r 'foo' src/ |
Grep(pattern="foo", path="src", -r=true) |
cat/head/tail on a file |
Read — use offset/limit to page through |
echo ... > file / cat > file |
Write(file_path=..., content=...) |
git add . / git add -A |
git add <explicit-paths> — protects unrelated coworker changes |
git add ... && git commit ... |
Two separate Bash calls — git's index.lock does not survive && |
Read before Edit/Write. The harness tracks read-state per agent thread. Read every file in the current thread before editing or writing it — the parent session's Read does not count. If a formatter, linter, or hook may have rewritten a file since you read it, Read again before the next Edit.
Scope
- Input: Search pattern, replacement text, optional file scope (glob pattern, directory, file list)
- Output: Modified files with replacement count summary
- Steps: 3-10, focused replacements
- Value: Eliminates cross-platform sed issues (
-iflag differences), permission prompt friction, and hook blocks entirely
Workflow
- Search — Use Grep to find all matches across the codebase. Use Glob to scope to specific file patterns if requested. Record the full match list (path + count) from Grep in your own working notes — that list is the checklist you tick off, and it is reproduced verbatim under
### Files Modifiedin the final report. - Preview — For ambiguous patterns (short strings, common identifiers), use Read to inspect context around matches before replacing. Skip this step for unambiguous patterns.
- Replace — Use Edit with
old_string/new_stringfor each file. Usereplace_all: truewhen the same literal substitution appears multiple times in a file. Mark each file complete in your match list. - Verify — Use Grep to confirm zero remaining matches. Report summary.
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.
- 1mo ago Changed 9dd9fc22f433
- 1mo ago First seen · 114 lines · 37 tokens per session scan A faa6d872b0b2
search-replace is an agent published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,374 once invoked, about $0.0001 per session on Opus 5.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
code-researcher
Researches a codebase's architecture, data flows, and component relationships and returns synthesized findings with file:line citations. Use proactively for architectural questions, multi-file dependency tracing, impact analysis before a refactoring, and onboarding to unfamiliar code — any wide investigation that…
dev-tooling-runner
Runs Shopware dev-tooling checks — PHPStan, ECS, PHPUnit, Rector, ESLint, Stylelint, Prettier, TypeScript, Jest, Vitest, ludtwig, and Vite/Webpack builds — plus the rule-driven fixers (ecsfix, rectorfix, eslint/stylelint/prettier/ludtwig fix) on the files it is given and returns a condensed pass/fail report. Use when…
theme-extractor
Analyzes interview transcripts to identify recurring themes and patterns.
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
guardrail-checker
Use this agent to verify that code changes follow development guardrails -- git safety, security practices, PR workflow, and coding standards. Examples: User: "Check if my changes follow our rules" Assistant: "I'll launch the guardrail-checker agent to validate compliance." User: "Audit this PR for best practice…
doc-writer
Generate or update documentation from code changes - changelogs, API docs, migration guides. Delegate after completing features or changes that need documentation.