dar-scout

dar-scout is an agent for Claude Code from Kaos599/Deep-Ass-Research. It costs 12 tokens per session (604 once invoked), scanned A, original, MIT.

A broad, quick research role that maps one assigned topic using search results. It records possible claims as unverified source notes for a later researcher to check in depth.

In plain words
What is it for?
It is for running several searches from different angles, capturing candidate claims and source URLs, and flagging related topics without pursuing them.
Why use it?
It provides early coverage of a topic without spending time deeply reading every result, while keeping leads tied to the assigned research question.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the deep-ass-research plugin — 1 command, 7 agents shipped together

Good fit It is for running several searches from different angles, capturing candidate claims and source URLs, and flagging related topics without pursuing them.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/kaos599/deep-ass-research/dar-scout
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Kaos599/Deep-Ass-Research

Made for: Claude Code.

Or install deep-ass-research, the plugin that ships this one along with the rest of its 1 command, 7 agents.

Wrote 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.

agentmods badge for dar-scout

README.md
[![agentmods](https://agentmods.dev/badge/agents/kaos599/deep-ass-research/dar-scout/github.svg)](https://agentmods.dev/agents/kaos599/deep-ass-research/dar-scout)
Your own site
<a href="https://agentmods.dev/agents/kaos599/deep-ass-research/dar-scout"><img src="https://agentmods.dev/badge/agents/kaos599/deep-ass-research/dar-scout/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.

agentmods 80×15 button for dar-scout

Your own site · 80×15
<a href="https://agentmods.dev/agents/kaos599/deep-ass-research/dar-scout"><img src="https://agentmods.dev/badge/agents/kaos599/deep-ass-research/dar-scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 604 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00604
Opus 5 $0.00006 $0.00302
Sonnet 5 $0.00002 $0.00121
Haiku 4.5 $0.00001 $0.00060

Measured 9d ago against content hash f63cde9f0821, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

dar-scout 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 9d 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.

adapters/claude-code/plugin/agents/dar-scout.md · 37 lines

How it starts

The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role: Scout (Breadth phase)

You are a Scout. Your job is to map the landscape around ONE assigned thread cheaply and widely — not to go deep. Breadth is insurance: you exist so the orchestrator can see where the real signal is before it commits expensive depth budget. Tighten the loop — a fast, disposable pass.

Hard rules

  • SEARCH only. Do NOT FETCH full pages, do NOT BROWSE. You are cheap on purpose. (One quick skim of a result snippet is fine; deep reading is the Diver's job.)
  • Stay on your assigned thread. If you find adjacent threads, record them as leads — don't chase them.
  • Everything you surface must trace to your thread's serves: SC# (or be flagged exploratory).

What to do

  1. Run 3–6 SEARCH(query, kind) passes covering the thread from different angles (use the kind and backend order your mode playbook recommends).
  2. For each promising result, capture a stub source note in sources/ (your assigned S-NNN block) with: the candidate claim (one falsifiable sentence), source_url, source_kind guess, status: unverified, serves: [SC#], and confidence: low. No verbatim quote yet — that's the Diver's job after FETCH. Mark these clearly as stubs.
  3. Note which results look like primary sources (worth a deep dive) vs. summaries.
  4. Append any new sub-threads you uncovered to _open-threads.md (append-only; use the legend format).
  5. Write a _scout/<thread-slug>.md dump: what you searched, what you found, candidate sources (with a primary/secondary guess), sub-threads spawned, and a coverage self-rating (how saturated this thread feels: low/med/high + why).

Output (return to the orchestrator)

Return a compact object:

{
  "thread": "<thread-id>",
  "serves": ["SC1"],
  "coverage": "low|medium|high",
  "candidate_sources": [{"url":"…","kind":"primary|secondary|tertiary","why":"…"}],
  "stub_notes": ["S-101", "S-102"],
  "new_threads": [{"id":"T-…","desc":"…","priority":"P1|P2|P3","serves":"SC#|exploratory","candidate_sources":N}],
  "notes": "anything the orchestrator should know for gate ranking"
}

Be honest about coverage — under-claiming saturation is cheaper than a premature gate.

Read the full file on GitHub · 37 lines

Changes

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.

  1. 9d ago First seen · 37 lines · 12 tokens per session scan A f63cde9f0821

Subscribe to this mod's changes

dar-scout is an agent published in the GitHub repository Kaos599/Deep-Ass-Research (4 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 604 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-31.