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/pedrogiudice/lex-vector/deep-researchgit clone --depth 1 https://github.com/PedroGiudice/lex-vectorWrote 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/pedrogiudice/lex-vector/deep-research)<a href="https://agentmods.dev/commands/pedrogiudice/lex-vector/deep-research"><img src="https://agentmods.dev/badge/commands/pedrogiudice/lex-vector/deep-research.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.00000 | $0.00654 |
| Opus 5 | $0.00000 | $0.00327 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
deep-research 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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Command: Deep Research
Execute the Gemini ADK Deep Research Agent for autonomous technical research with web search grounding.
Usage
/deep-research "Your research topic here"
Or with arguments:
/deep-research --check # Check dependencies only
/deep-research --help # Show help
What This Command Does
- Validates that the Gemini ADK environment is properly configured
- Executes the Deep Research Agent with the provided topic
- The agent autonomously:
- Generates multiple search queries
- Retrieves information from the web via Google Search grounding
- Synthesizes findings into a structured technical report
- Saves results to
adk-agents/deep_research_sandbox/research_output/
Execution
When the user invokes this command, execute:
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "/home/cmr-auto/claude-work/repos/lex-vector")
cd "$REPO_ROOT/adk-agents" && ./run-research.sh "$ARGUMENTS"
If $ARGUMENTS is empty, ask the user for a research topic.
If $ARGUMENTS is --check, run:
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "/home/cmr-auto/claude-work/repos/lex-vector")
cd "$REPO_ROOT/adk-agents" && ./run-research.sh --check-deps
Prerequisites
GOOGLE_API_KEYenvironment variable (loaded fromadk-agents/.env)- Python virtual environment at
adk-agents/deep_research_sandbox/.venv/ - Required packages:
google-adk,google-genai,tenacity
Output Format
Research results are saved as Markdown with:
- Key Findings: Bulleted facts with citations
- Technical Specifications: Data tables
- Data Conflicts / Uncertainties: Noted discrepancies
- Source Index: Full citations
Examples
Basic research:
/deep-research "Compare vector databases: Pinecone vs Weaviate vs Milvus"
Technical analysis:
/deep-research "Latest developments in transformer attention mechanisms 2026"
Check setup:
/deep-research --check
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.
- 3d ago First seen · 90 lines · 0 tokens per session scan A acea762dab14
deep-research is a command published in the GitHub repository PedroGiudice/lex-vector (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 654 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.