claude

research-toolkit

Even-handed investigation of loaded, contested topics. Research & investigation skills for thinking-with-AI - investigation protocols (deep-investigation, cui-bono / "follow the money", screening a dev job or employer for hidden military/defense ties), text & source deconstruction, frame rotation, and iterative verification that escalates to a recursive adversarial dialectic (generate a claim's exact opposite and test it). The skepticism is symmetric - turned on the consensus, the contrarian take, the model's own bias, and its own conclusions; it assumes no villain in advance (POSIWID: judge a method by what it does, not what it claims). Ships two deliberately basic MCP servers - thin data-access layers, not analysis engines; the skills do the analysis: financial-mcp (stock price, history, company info and standard technical indicators via yfinance, with a local ticker cache) and transparency-mcp (keyless public data - US Congress bills/members/votes via GovTrack, World Bank development indicators, and US nonprofit Form 990 filings via ProPublica).

2 on GitHubby bogheorghiuv4.8.0MITupdated 3 days ago
/

Plugin research-toolkit from marketplace ex-cog-dev in bogheorghiu/ex-cog-dev. Commands read from the repo's manifest — 3 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (22)

  • cui-bono

    Who actually benefits — and at whose expense? Power structure analysis for any domain: geopolitics, corporate behavior, institutional claims, media narratives. Use when (1) who benefits from X, (2) ownership or revolving doors, (3) are these sources independent or echoing one origin, (4) expert has

  • deep-investigation-protocol

    What is REALLY at stake here? And for whom?" - STOP. When the matter involves trustworthiness, purchasing decisions, "which is better or more reliable", brand comparisons, marketing claims, corporate behavior, "convince me otherwise", or post-purchase "was this good?" - USE THIS. For technical specs

  • dev-job-defense-ties

    Evaluating a dev job, studio, or employer? Before taking it, screen who the work actually serves — is it military/defense behind civilian language, and is the buyer one your red line rules out? Runs cui-bono for the buyer-chain, then classifies by end-use and buyer-nationality against YOUR threshold

  • dialectic-spiral

    Am I agreeing because it SOUNDS right, or because it IS right? Recursive adversarial dialectic for testing any claim, finding, or synthesis against its own opposite. Use when convergence feels too easy, when findings need stress-testing, or when any research skill escalates to dialectic depth.

  • engage-the-disfavored

    Did I judge this before reading it?" - Counter the valence reflex: a fact-based analysis whose conclusion favors a disfavored party (an adversary state, an accused figure, a label-discredited source) gets pre-discounted by provenance before its facts are engaged. Separate provenance from factual tru

  • frame-rotation

    「透镜」 What structure hides in my native grammar? Linguistic frame rotation to escape English-default pattern-recognition. Use when (1) pattern-recognition feels stuck in familiar grooves, (2) abstraction circles without grounding, (3) cross-domain insight feels like same-OS-different-domain, (4) trig

  • ground-level-triangulation

    What do the people with different stakes say, in their own languages?" - Map a contested geopolitical claim across language-publics with different, independent stakes: the implicated state's own primary documents, the affected party's language and nearest kin languages, non-official native voices, n

  • iterative-verification

    Is this ACTUALLY verified, or did I just say it is?" - Factual accuracy verification loop. Use when (1) claims require evidence not assumption, (2) verification must be demonstrable, (3) single-pass investigation insufficient, (4) factual accuracy is critical. Provides the loop logic: iterate until

  • kernel-shell

    What part of this thesis is observation, and what part is story?" - Decompose a contrarian or heterodox thesis into atoms; classify each atom (observation / inference / intent-attribution / satellite); verdict each atom on its own evidence — never the thesis as a bundle. Use when (1) evaluating a th

  • label-function-analysis

    What is this label DOING?" - Unbundle a loaded label (extremist, denier, conspiracy theorist, apologist, shill) into observation, intent, mechanism, and actor; autopsy the debate axis the label enforces; run cui-bono on the label itself; test whether the replacement axis is falsifiable. Use when (1)

  • macro-monitor

    What is moving in the macro picture? Geopolitical/macro market indicators. Use when (1) China/US Treasury dynamics, (2) dollar-yield divergence, (3) Brent crude oil / energy price spikes, (4) geopolitical market risk, (5) one-command crisis check. NOT for stock analysis or fundamentals.

  • manufactured-confusion-detection

    Is this fog organic, or engineered?" - Inverse of manufactured-consensus-detection: test whether noise, contradiction, and over-supplied mutually exclusive explanations around a claim are organic uncertainty or engineered to prevent ANY conclusion. Use when (1) every source tells a different story w

  • manufactured-consensus-detection

    Are these sources agreeing independently, or echoing the same origin?" - When multiple sources converge on the same claim in similar language, test whether this is genuine independent agreement or coordinated messaging from a single origin. Use when (1) multiple independent sources say the same thin

  • research

    Where should I start investigating this? Routes research questions to the right methodology based on topic domain, depth needed, and available sources. Use when the research question spans multiple domains or the appropriate methodology is unclear. Not needed when a specific skill (DIP, cui-bono, yo

  • saturation-sweep

    What hasn't the sweep reached yet?" - Horizontal iteration in waves over declared branching axes (who else, where else, when else, who benefits elsewhere), with a novelty ledger per wave and a measured stop rule. Use when (1) an investigation risks stopping at the first coherent story, (2) "done sea

  • source-dossier

    Who is this source, structurally?" - Classify a source by four observable grounds (its own content over time; ownership and registries; declared self-positioning; dated case behavior) before weighing its claims, and keep an append-only per-source dossier across investigations. Use when (1) a source

  • source-omission-analysis

    What is everyone NOT saying about this?" - After any multi-source research sweep, analyze what each perspective is SILENT about. Omissions reveal structural position more reliably than statements. Use when (1) after completing multi-source research, (2) comparing coverage across ideological position

  • standpoint-pass

    Who is most affected here, and what did the text do to them?" - Re-read primary material from the position of the most-affected, least-powerful party, and re-rank what matters by harm-to-the-many instead of offense-to-the-powerful. Use when (1) analyzing a speech, document, policy, or transcript who

  • substack-research

    What are the independent voices actually saying? Extract and analyze long-form content from Substack publications. Use when (1) researching independent journalist perspectives, (2) analyzing a specific Substack publication, (3) building a research corpus from long-form written content, (4) cross-ref

  • text-deconstruction

    Where does this text need what it excludes? Finds where texts undermine themselves on their own terms via close reading. Use when (1) analyzing arguments, policies, or frameworks claiming coherence, (2) something feels off but unnameable, (3) a framework presents itself as complete, (4) user asks wh

  • video-transcript-extraction

    How do I get the transcript of this video? Platform-aware extraction for any video source — YouTube, local files, or other platforms. Use when (1) need to transcribe a video for analysis, (2) user provides a video URL, (3) building a knowledge base from video content. Provides multiple methods with

  • youtube-research

    What do practitioners actually DO (not just document)? Methodology for extracting practitioner knowledge from YouTube video transcripts. Use when (1) researching how people actually use a technology, (2) seeking practitioner insights beyond documentation, (3) looking for tips, patterns, or workflows

Slash commands (2)

  • /research-toolkit:firing-filter

    Control the deterministic firing layer: status | on | off (per session)

  • /research-toolkit:substack-extract

    Extract and parse Substack articles with AI analysis

Subagents (4)

  • adversarial-critic

    Did I just agree because it SOUNDED right?" - Adversarial critic for investigation teams. Reads researchers' output files and runs the generative dialectic spiral — generating the exact OPPOSITE of each synthesis, then testing it. Use when (1) investigation teams need adversarial challenge, (2) find

  • falsifier

    What here is NOT actually working?" - Adversarial verification agent that seeks disconfirmation. Designs and runs falsification tests against claims, implementations, and completion criteria. Use when (1) verifying implementation claims match reality, (2) stress-testing completion criteria before ma

  • investigation-orchestrator

    Who needs to look at this, from where, and what are they not seeing?" - Orchestrates full multi-agent investigations. Takes a topic, designs the team, assigns source-position scopes, deploys researchers + adversarial critic, manages dialectic rounds, and produces final synthesis with evidence tiers

  • negative-dialectical-spiral

    Hold the contradiction open — do not resolve. Maps where concepts fail against particulars via context-isolated tension tracking. Use when (1) synthesis feels too neat, (2) need what a frame cannot capture, (3) dialectic-spiral resolves when it should hold open. NOT for binary questions, stress-test

MCP servers (2)

  • financial-mcp

    runs: uvx --from git+https://github.com/bogheorghiu/ex-cog-dev#subdirectory=research-toolkit/mcp-servers/financial-mcp financial-mcp

  • transparency-mcp

    runs: uvx --from git+https://github.com/bogheorghiu/ex-cog-dev#subdirectory=research-toolkit/mcp-servers/transparency-mcp transparency-mcp

Hooks (8)

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/hooks/count-skill-firings.sh"

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/hooks/firing-filter/firing-filter-hook.sh" pre-agent

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/hooks/firing-filter/firing-filter-hook.sh" pre-write

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/hooks/firing-filter/firing-filter-hook.sh" post-agent

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/hooks/firing-filter/firing-filter-hook.sh" post-write

  • UserPromptSubmit

    "${CLAUDE_PLUGIN_ROOT}/hooks/firing-filter/firing-filter-hook.sh" user-prompt

  • Stop

    "${CLAUDE_PLUGIN_ROOT}/hooks/firing-filter/firing-filter-hook.sh" stop

  • SessionStart

    "${CLAUDE_PLUGIN_ROOT}/hooks/firing-filter/firing-filter-hook.sh" session-start

View source on GitHub

More from bogheorghiu/ex-cog-dev

All 4 plugins →

A working proof of concept for catching the same structure in places that have nothing to do with each other - and in your own working process: notice such a regularity, capture it, and test each for a real shared mechanism, not surface resemblance. Today it's a growing, hand-kept list of specific observations that resurface when the shape shows up again, each accumulating a count of the times it has recurred. The self-organizing learner the system is built toward is the genuine direction, not yet the state - an early, already-useful step toward it. Memory for forms, not just facts; two local MCP servers (relational-memory + a usage-weighted knowledge graph, experimental). The term "vasana" is grounded in the plugin's axioms.

10 skills · 1 command · 1 agent · 2 MCP servers · hooks

2

Discipline for prompting and co-authoring with AI - nothing to configure, just skills. intrinsic-prompt-design: give the model the reason behind a rule, not just the rule; the reasons part clearly helps, even paired with plain imperatives, though so far only anecdotally (rigorous testing is still worth doing), and its bolder idea - deliberately leaving space for the model's own agency to fill - is the core experimental proposition. system-pilot: engineering discipline for deterministic systems, adapting the original Universal CLAUDE.md Protocol. skill-activation-testing: a two-tier A/B (cheap proxy + live firing test) for whether a description change actually fires, with the validity limit of each tier named, plus a stdlib scorer over claude plugin eval that adds case-level intervals, paired arm deltas and a pre-registered ship rule.

3 skills · 2 agents

2

Useful friction against obvious mistakes - a basic draft, not a security product (no sandbox; whatever doesn't match a pattern passes through). Threat-detection and dangerous-action-blocking hooks for Claude Code: prompt-injection detection (tiered, with allowlist; covers MCP tool outputs via the * matcher), block dangerous git operations (push to main, force push, reset --hard, --no-verify, etc.), and Desktop Commander input safeguards (block start_process and set_config_value). Also ships an optional, per-user PR-merge guard - block Claude from running `gh pr merge` so a human always merges - that is OFF by default and toggled with the `/pr-merge-guard` command (on/off/status); the `pr-merge-guard` skill explains it and flips it on request. New: the `windows-wsl-security-verification` skill - a guided "am I compromised?" IOC triage + attack-surface reduction for Windows + WSL2 dev boxes after a supply-chain scare (poisoned npm/PyPI package, trojaned extension), with the detection-reading discriminators that prevent false alarms. Windows/WSL-specific; verifies, does not harden; a clean result raises confidence, never proves. Also ships the `pii-gate` skill and installer - a drop-in PII/secret gate for a git repo (pre-commit + pre-push hooks + a CI workflow) that blocks personal names from reaching a remote and chains gitleaks for secrets. It fires on `git init`, adding a remote, or a first push, because pushed history is permanent and the gate only works if it exists before that first push. Everything fails closed, matching is case-insensitive and whole-word in every layer, the CI denylist secret lives in a GitHub Environment limited to the default branch so no branch run can read it, gitleaks in CI ignores inline allow comments and repo-root config, a matched term is never echoed, and the shipped denylist template is EMPTY by design - you fill in a gitignored copy, nothing personal ever lives in the repo.

3 skills · 1 command · hooks

2

Maintain research-toolkit?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins4 plugins