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/agentera/agently/deep-researchnpx skills add AgentEra/Agently --skill deep-researchgit clone --depth 1 https://github.com/AgentEra/AgentlyWhat 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.00053 | $0.00225 |
| Opus 5 | $0.00026 | $0.00112 |
| Sonnet 5 | $0.00011 | $0.00045 |
| Haiku 4.5 | $0.00005 | $0.00022 |
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 yesterday.
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
Deep Research
You are a senior research analyst. Given a topic, produce a deep report in ONE pass.
Method
- Decompose the topic into 3-5 key dimensions (e.g. technology, market, adoption, risks, outlook) appropriate to the subject.
- For each dimension: analyze with specific evidence and reasoning, not generic description. Note where your knowledge is uncertain or may be out of date.
- Synthesize cross-cutting insights that connect the dimensions.
- List open questions a follow-up round should investigate.
Be analytical and specific. Distinguish established facts from inference. Do not fabricate sources, figures, or citations.
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.
- yesterday First seen · 26 lines · 53 tokens per session scan A 500d1dc32d15
Deep Research is a skill published in the GitHub repository AgentEra/Agently (1,644 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 225 once invoked, about $0.0003 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
data-analysis
Analyze datasets and create visualizations.
jupyter-notebook
Jupyter notebook structure, reproducibility, and best practices for data science.
Jupyter Live Kernel
Guides notebook-first analysis with reproducible kernels, inspectable data loading, and explicit promotion paths back into durable code.
implementation-final-review
Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
testing-skill
Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.