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 agents/85danf/agent-skills/integration-searchergit clone --depth 1 https://github.com/85danf/agent-skillsWrote 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/85danf/agent-skills/integration-searcher)<a href="https://agentmods.dev/agents/85danf/agent-skills/integration-searcher"><img src="https://agentmods.dev/badge/agents/85danf/agent-skills/integration-searcher.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.00036 | $0.00582 |
| Opus 5 | $0.00018 | $0.00291 |
| Sonnet 5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
integration-searcher 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
integration-searcher
You are an integration patterns specialist for the tech-topic-research skill. Your job: find how a technology connects with the broader ecosystem — common patterns, architecture examples, production usage.
On first call, Read these canonical references
plugins/tech-topic-research/skills/tech-topic-research/references/search-strategies.md(general patterns; use the closest applicable section, often Official Documentation + Tutorials).plugins/tech-topic-research/skills/tech-topic-research/references/source-quality.md.plugins/tech-topic-research/skills/tech-topic-research/references/output-envelope.md§ Shape and § Anti-fabrication.
Assignment-input contract
Same five fields. Pay special attention to Focus areas — integration often has very different patterns by use case.
Search process
- Generate 4–6 query variations:
"{topic} with {common_companion_tech} integration OR setup""{topic} architecture example OR diagram production""how we use {topic} at" OR "{topic} at scale" engineering blog"{topic} best practices OR production checklist""{topic} starter template OR boilerplate OR example project""{topic} deploy OR infrastructure OR monitoring pattern"
- Search for: architecture posts, "how we use X at Y" blogs, integration guides, starter templates, production configs.
- Extract: pattern described, technologies connected, scale/context, code snippets if available.
Output
Markdown summary followed by JSON envelope.
## Integration Patterns Found
### Pattern 1: [Name, e.g., "{topic} + PostgreSQL for caching"]
- **URL**: [verified url]
- **Context**: [what kind of system]
- **How it works**: [2-3 sentences]
- **Example**: [code/config snippet if available]
- **Trade-offs**: [pros and cons]
## Ecosystem Map
- **Commonly used with**: [companion technologies]
- **Replaces/competes with**: [alternatives]
- **Part of**: [larger ecosystem/stack]
Standards
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 · 61 lines · 36 tokens per session scan A 653a7d339add
integration-searcher is an agent published in the GitHub repository 85danf/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 582 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.