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 skills/autohandai/code-cli/deep-researchnpx skills add autohandai/code-cli --skill deep-researchgit clone --depth 1 https://github.com/autohandai/code-cliWhat 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.00021 | $0.00449 |
| Opus 5 | $0.00010 | $0.00225 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
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 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.
What it actually says
You conduct iterative, multi-source deep research and produce a reusable cited research report.
Scope The Question
- Restate the user's research topic or question in concrete terms.
- Identify 4-8 subquestions that would fully answer it.
- Ask at most one clarifying question only when the topic is too ambiguous to research safely.
- Track the research phases and subquestions with
todo_write.
Gather Evidence
For each subquestion:
- Use
web_searchto discover current sources. - Use
fetch_urlto read the strongest sources instead of relying on snippets. - Prefer primary sources, official documentation, papers, standards, release notes, or direct project/company material.
- Record each source URL, source title, publication date when available, fetched date, and confidence.
- Look for disagreement, stale claims, and missing context.
- Continue pulling threads until every subquestion is answered or the gap is explicitly documented.
Use tool_search to find available agent, task, or parallel research tools when the research topic is broad enough to benefit from delegation.
Synthesize
- Cross-check load-bearing facts against at least two independent sources when possible.
- Note whether evidence is recent, historical, speculative, or contradicted.
- Resolve contradictions when the evidence supports a resolution; otherwise flag them.
- Keep unverified claims out of the report.
Report
Write a self-contained markdown report to the path supplied by the slash command.
Required sections:
# <clear title>## Summary## Findings## Open questions / uncertainty## Sources
Findings must be organized by theme or subquestion and include inline numbered citations like [1].
The Sources section must number every cited source and include title, URL, publication date if known, and fetched date when useful.
Do not stop until the report is saved with write_file and the final response includes the exact saved path.
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 · 53 lines · 21 tokens per session scan A 4f3638352827
deep-research is a skill published in the GitHub repository autohandai/code-cli (181 stars, last pushed 6d ago), licensed Apache-2.0. It adds 21 tokens to every session and 449 once invoked, about $0.0001 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-30.
Other skills, from other repositories
neuron-test-engineer
Write tests for Neuron AI agents, RAG systems, workflows, and tools using the built-in testing utilities. Use this skill when the user mentions testing agents, writing unit tests, mocking AI providers, testing tool execution, verifying RAG retrieval, testing workflow behavior, or creating test cases for Neuron AI…
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
neuron-structured-output
Design and implement structured output classes for Neuron AI agents using SchemaProperty attributes and validation rules. Use this skill when the user mentions structured output, JSON schema extraction, data validation, output classes, DTOs for AI responses, extracting structured data from LLM, or configuring property…
neuron-agent-builder
Create and configure Neuron AI agents with providers, tools, instructions, and memory. Use this skill whenever the user mentions building agents, creating AI assistants, setting up LLM-powered chat bots, configuring chat agents, or wants to create an agent that can talk, use tools, or handle conversations. Also…
neuron-debugger
Debug and monitor Neuron AI applications with Inspector APM, event observability, logging, and performance analysis. Use this skill whenever the user mentions debugging, monitoring, observability, performance analysis, tracing, Inspector, or needs to understand why an agent is behaving a certain way. Also trigger for…
neuron-rag-specialist
Implement RAG (Retrieval-Augmented Generation) with Neuron AI including vector stores, embeddings providers, document loaders, and retrieval strategies. Use this skill whenever the user mentions RAG, retrieval, vector search, document retrieval, semantic search, knowledge bases, chat with documents, or wants to build…