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.
git clone --depth 1 https://github.com/Kaos599/Deep-Ass-ResearchWrote 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/agents/kaos599/deep-ass-research/dar-scout)<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.
<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>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.00012 | $0.00604 |
| Opus 5 | $0.00006 | $0.00302 |
| Sonnet 5 | $0.00002 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00060 |
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.
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
SEARCHonly. Do NOTFETCHfull pages, do NOTBROWSE. 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 flaggedexploratory).
What to do
- Run 3–6
SEARCH(query, kind)passes covering the thread from different angles (use thekindand backend order your mode playbook recommends). - For each promising result, capture a stub source note in
sources/(your assignedS-NNNblock) with: the candidate claim (one falsifiable sentence),source_url,source_kindguess,status: unverified,serves: [SC#], andconfidence: low. No verbatim quote yet — that's the Diver's job afterFETCH. Mark these clearly as stubs. - Note which results look like primary sources (worth a deep dive) vs. summaries.
- Append any new sub-threads you uncovered to
_open-threads.md(append-only; use the legend format). - Write a
_scout/<thread-slug>.mddump: 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.
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.
- 9d ago First seen · 37 lines · 12 tokens per session scan A f63cde9f0821
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.
Other agents, from other repositories
project-init
Initializes Agentic SEO project with the required folder layout, blank brain templates, contents directories, and first log entry. Use when creating a new project.
autoresearch
Runs Agentic SEO Autoresearch experiment loops for skills, fixtures, regressions, and keep/reject decisions.
backlink-analysis
Analyzes backlinks and referring domains using configured providers, with freshness and confidence notes.
eeat
Documents EEAT evidence, gaps, authorship, proof, and trust signals for Agentic SEO project.
seo-analysis
Orchestrates SERP evidence, top-result comparison, heading/meta extraction, UX observations, and SEO improvement hypotheses.
keyword-research
Runs keyword research with DataForSEO when enabled and produces normalized keyword evidence for clusters and content.