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 skills add synaptiai/synapti-marketplace --skill deep-researchgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/skills/synaptiai/synapti-marketplace/deep-research)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/deep-research"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/deep-research/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/deep-research"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/deep-research.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.02280 |
| Opus 5 | $0.00028 | $0.01140 |
| Sonnet 5 | $0.00011 | $0.00456 |
| Haiku 4.5 | $0.00006 | $0.00228 |
Grade A, and why
conducting-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 12d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conducting Deep Research
This skill uses an iterative methodology treating research as a diffusion process: start with noise (rough draft), apply guidance (research brief), denoise through cycles of critique → research → refine until quality converges.
Use TodoWrite to track these mandatory steps:
Step 1: Clarify Scope
Ask me clarifying questions only if:
- Topic has multiple interpretations
- Key constraints missing (timeframe, geography, industry)
- Success criteria unclear
Skip for well-defined requests.
Step 2: Research Brief (Guidance Signal)
RESEARCH BRIEF
Topic: [Specific question]
Scope: [Included/excluded]
Key Questions:
1. [Primary]
2. [Secondary]
3. [Tertiary]
Constraints: [Limits]
Language: [Match user's language]
Step 3: Initial Draft (Noisy Starting Point)
Write from existing knowledge only, marking gaps:
[NEEDS VERIFICATION]- uncertain claims[RESEARCH NEEDED]- missing information[CONFIDENCE: LOW/MED/HIGH]- flag uncertainty levels
This draft intentionally contains "noise" - the refinement loop will denoise it.
Step 4: Red Team Critique
Attack the draft for:
- Logic: Circular reasoning, false dichotomies, unsupported claims
- Gaps: Missing perspectives, incomplete coverage
- Sources: Unsourced claims, single-source reliance
Rate each issue 1-10 severity. See references/critique-framework.md.
Step 5: Targeted Research with Reflection
Search budget by complexity:
- Simple verification: 1-2 searches
- Moderate topics: 3-5 searches
- Complex research: 5-10 searches
CRITICAL: Think after EVERY search. After each web_search, pause and reflect:
REFLECTION:
- What key facts did I find?
- What gaps remain?
- Do sources agree or conflict?
- Is another search needed, or do I have enough?
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 307 lines · 55 tokens per session scan A 611c4aa85450
conducting-deep-research is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 2,280 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-31.
Other skills, from other repositories
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
plan-product
Define product mission, vision, target users, and technology stack.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.