By Kaos599
Deep Ass Research (DAR) — deep, multi-source, primary-sourced research into a backlinked Obsidian vault: fan-out scout/diver subagents, adversarial verification, and a synthesized Map-of-Content + report.
DAR — Librarian (Synthesize phase, structural pass)
DAR — Relevance Monitor (Drift Guard, step 4.5)
DAR — Scout (Breadth phase)
DAR — Skeptic (Verify phase)
DAR — Synthesizer (Synthesize phase — the deliverable)
External network access
Connects to servers outside your machine
Requires secrets
Needs API keys or credentials to function
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses power tools
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
Research like a paranoid PhD, not a search bar.
Maps a topic wide, commits to depth on purpose, tries to refute its own findings, and leaves you a backlinked, primary-sourced knowledge vault — in any AI coding agent.
Before / After • How it works • Install • What you get • Full install guide
Most "research" an agent does is one search, three skimmed snippets, and a confident paragraph that may or may not be true. DAR runs the loop a careful human would: cast wide, decide where to go deep, read the primary source (not the thread about it), send skeptics to disprove every load-bearing claim, and write it all into an Obsidian vault where every sentence traces to a source you can re-open.
It's host-agnostic: the methodology is plain markdown (core/), and thin adapters bind it to Claude Code, Cursor, opencode, or anything that reads AGENTS.md.
You ask: "How much revenue does Perplexity make and what's their strategy?"
🔍 Normal agent
One search. No source. No idea if it's current, self-reported, or made up. |
🤿 DAR
|
Same question. One is a vibe. The other is a defensible, navigable answer you can audit.
DAR has two halves that share one spine — the charter (what we're actually trying to answer). A gate stops it from going deep too early; a drift guard stops it from wandering once it's deep. The charter is a compass, not a cage: useful tangents get promoted, dead ones pruned.
flowchart TD
A(["📥 Research request"]) --> P["0 · Preflight<br/>bind capability verbs to host tools"]
P --> C["1 · Decompose & Charter<br/>success criteria SC1…SCn · scope · clarify with user"]
C --> B["2 · Breadth<br/>parallel SEARCH-only scouts map the landscape"]
B --> G{"Gate<br/>saturated? · rankable?<br/>anchors hit?"}
G -->|widen one wave| B
G -->|too broad: narrow| C
G ==>|human check-in| D["3 · Depth loop<br/>divers FETCH full primaries<br/>→ atomic, cited claim notes"]
D --> DG{"4.5 · Drift Guard<br/>still serving the charter?"}
DG -->|CONTINUE| D
DG -->|REFOCUS: prune / promote| D
DG -->|ESCALATE: ask the user| C
DG ==>|CONCLUDE| V["4 · Verify<br/>3 skeptics try to refute · 2-of-3 majority<br/>→ arbiter breaks ties"]
V --> S["5 · Synthesize<br/>librarian links & dedupes → synthesizer writes the map"]
S --> O(["📦 Deliver<br/>Map-of-Content · report · open questions"])
classDef phase fill:#0f172a,stroke:#334155,color:#e2e8f0;
classDef gate fill:#fde68a,stroke:#b45309,color:#1c1917;
classDef done fill:#bbf7d0,stroke:#15803d,color:#052e16;
class P,C,B,D,V,S phase;
class G,DG gate;
class A,O done;
The principles behind each step (why they exist) — straight out of how good researchers actually work:
SEARCH-only scouts first; expensive FETCH only on threads that survive the gate.raw/; a claim sourced only to a summary is quarantined._MOC.md + [[wikilink]] graph + a report answering each criterion — not a wall of text.npx claudepluginhub kaos599/deep-ass-research --plugin deep-ass-researchComprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Memory compression system for Claude Code - persist context across sessions