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/marcusquinn/aidevops/deep-researchgit clone --depth 1 https://github.com/marcusquinn/aidevopsWrote 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/marcusquinn/aidevops/deep-research)<a href="https://agentmods.dev/commands/marcusquinn/aidevops/deep-research"><img src="https://agentmods.dev/badge/commands/marcusquinn/aidevops/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.00013 | $0.01119 |
| Opus 5 | $0.00006 | $0.00560 |
| Sonnet 5 | $0.00003 | $0.00224 |
| Haiku 4.5 | $0.00001 | $0.00112 |
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 4d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a cited, decision-grade research deliverable.
Arguments: $ARGUMENTS
Use /auto-research instead when the task is an autonomous experiment loop that
modifies files, measures a metric, and keeps or discards changes. Use
/deep-research when the output is a durable artifact: cited report, source
ledger, claim ledger, outline, and raw evidence bundle.
Invocation Patterns
| Pattern | Example | Behaviour |
|---|---|---|
| Topic | /deep-research "compare hosted vector databases for RAG" |
Infer scope and produce a report |
| Brief file | /deep-research --brief todo/research/vector-db-brief.md |
Read scope, questions, and constraints from file |
| Output dir | /deep-research "EU AI Act vendor obligations" --out todo/research/eu-ai-act |
Write deliverables to the requested directory |
| Headless | /deep-research --brief path/to/brief.md --out path/to/out |
Run without questions using the supplied scope |
Output Contract
Create an export bundle under todo/research/deep-{slug}/ unless --out is
provided:
todo/research/deep-{slug}/
├── source-plan.md # intended source classes and search strategy
├── sources.tsv # source ledger with URL/title/publisher/date/accessed/use
├── claims.tsv # claim ledger mapping claims to source IDs and confidence
├── outline.md # report structure before final synthesis
├── report.md # cited final report
└── raw/ # saved excerpts or fetched artifacts when safe and permitted
Workflow
Step 1: Scope
Parse topic, brief path, output path, deadline, geography, audience, and decision
to support. If no brief is supplied, infer a concise scope from $ARGUMENTS and
record it in source-plan.md. In headless mode, do not ask questions; document
assumptions in the plan.
Step 2: Source Plan
Write source-plan.md before collecting evidence:
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.
- 4d ago First seen · 142 lines · 13 tokens per session scan A 9a5e19571ea8
deep-research is a command published in the GitHub repository marcusquinn/aidevops (391 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,119 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 commands, from other repositories
auto
계획부터 PR까지 원버튼 자동 실행. 중간에 멈추지 않습니다.
sync
Command "sync" from sangrokjung/claude-forge, covering /sync - git pull + 문서 동기화, 플래그, phase 1: git pull (--no-pull 시 스킵), 1-1. 현재 상태 확인 and 1-2. pull 실행.
next-task
Command "next-task" from sangrokjung/claude-forge, covering /next-task - 다음 task 시작 준비 (v6), 0단계: 현재 상태 확인, 1단계: 진행률 계산, 2단계: 다음 task 식별 and 3단계: 복잡도 분석.
suggest-automation
반복 패턴 분석하여 자동화 기회 제안 (주기적 실행 권장).
guide
처음 사용자를 위한 인터랙티브 가이드. 약 3분이면 끝납니다.
eval
Manage eval-driven development workflow (define, check, report, list).