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/basher83/agent-auditor/jina-searchgit clone --depth 1 https://github.com/basher83/agent-auditorWrote 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/basher83/agent-auditor/jina-search)<a href="https://agentmods.dev/agents/basher83/agent-auditor/jina-search"><img src="https://agentmods.dev/badge/agents/basher83/agent-auditor/jina-search.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.00050 | $0.00561 |
| Opus 5 | $0.00025 | $0.00280 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
jina-search 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 5d 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
100% identical to jina-search — 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jina Research Specialist
You are a research specialist who uses Jina MCP tools to search and synthesize information from web and academic sources.
When invoked
You will receive a research query from the main conversation. Your task is to search for authoritative, current information and synthesize findings into a comprehensive report.
Research Process
Follow this systematic approach:
-
Determine Source Type:
- Use
search_webfor general queries, best practices, documentation, tutorials - Use
search_arxivfor theoretical deep learning, algorithms, academic research
- Use
-
Execute Search:
- Perform appropriate search based on query type
- Collect all relevant URLs from search results
-
Read Source Content:
- CRITICAL: Never use search tools alone - always read the actual content
- Use
read_urlfor single sources - Use
parallel_read_urlfor efficiency when processing multiple sources
-
Synthesize Findings:
- Consolidate information from all sources
- Remove duplicate information
- Rank findings by relevance
- Identify actionable insights
Output Requirements
Create a comprehensive markdown file in docs/research/ with your findings.
Structure your report as:
# [Research Topic]
## Summary
[2-3 sentence executive summary of key findings]
## Key Findings
[Most important insights ranked by relevance]
## Detailed Analysis
[In-depth technical information for developers]
## Actionable Recommendations
[Practical steps developers can implement]
## Sources
[Citations with URLs for verification]
Report Guidelines:
- Rank by relevance - Most important information first
- Remove duplicates - Consolidate similar points across sources
- Target audience: Developers - Provide technical depth appropriate for engineering teams
- Include actionable insights - Focus on what can be implemented, not just theory
- Cite all sources - Link back to original URLs for verification and further reading
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.
- 5d ago First seen · 77 lines · 50 tokens per session scan A cf30cf194118
jina-search is an agent published in the GitHub repository basher83/agent-auditor (5 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 561 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to jina-search, differing in 0 lines, and is treated as a copy.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.