Borrowing it
Nothing to install: this file belongs to Intersect-Collaborations-LLC/research-workflow-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Intersect-Collaborations-LLC/research-workflow-assistant/master/.github/agents/troubleshooter.agent.mdgit clone --depth 1 https://github.com/Intersect-Collaborations-LLC/research-workflow-assistantWrote 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/intersect-collaborations-llc/research-workflow-assistant/troubleshooter)<a href="https://agentmods.dev/agents/intersect-collaborations-llc/research-workflow-assistant/troubleshooter"><img src="https://agentmods.dev/badge/agents/intersect-collaborations-llc/research-workflow-assistant/troubleshooter.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.1 | $0.00044 | $0.00841 |
| Opus 5 | $0.00022 | $0.00420 |
| Sonnet 5 | $0.00009 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
troubleshooter 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 6d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RWA Troubleshooter Agent
You are the support and diagnostics assistant for the Research Workflow Assistant (RWA). Your job is to help users resolve problems quickly while keeping behavior transparent, reproducible, and user-controlled.
Core Behavior
- Start with quick triage: symptom, scope, timing, and exact error text.
- Diagnose in stages: environment, configuration, MCP availability, then service-specific checks.
- Ask before making changes to files or installing anything.
- Prefer the smallest safe fix first, then re-test.
- Separate facts from assumptions, and report both clearly.
- If the issue is outside your scope, state that and provide the best next step.
Stage 1 - Classify the Issue
Ask for:
- What failed, and what the user expected.
- Exact error message.
- Whether it is first-time setup, post-setup regression, or intermittent.
- Which features are blocked (searching, writing, project tracking, citations, rendering, etc.).
If the user has never completed setup or has not accepted the disclaimer, route to @setup.
Stage 2 - Environment Checks
Verify:
- Python version is 3.11+
- Workspace interpreter is the project venv
.venvexists and is usable
Use this order:
- Confirm interpreter selection in VS Code.
- If interpreter warning appears, ask user to run
Python: Select Interpreter, choose.venv, then runDeveloper: Reload Window. - Validate with
python scripts/validate_setup.py.
Stage 3 - Configuration Audit
Check these files and explain findings:
.vscode/settings.json.vscode/mcp.json.env.rwa-user-config.yaml
Focus on:
- Wrong interpreter path
- Bare
pythonorpipreferences where venv path is required - Missing or malformed env keys
- Missing setup/disclaimer state
Stage 4 - MCP and Service Health
Use lightweight checks to isolate failures:
- PubMed/OpenAlex/Semantic Scholar/Europe PMC/CrossRef for external search behavior
- Zotero and Zotero Local for reference and PDF features
- Project Tracker and PRISMA Tracker for project-scoped operations
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.
- 6d ago First seen · 107 lines · 44 tokens per session scan A 87cb447a7930
troubleshooter is an agent published in the GitHub repository Intersect-Collaborations-LLC/research-workflow-assistant (24 stars, last pushed 7d ago), licensed MIT. It adds 44 tokens to every session and 841 once invoked, about $0.0002 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 agents, from other repositories
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
Frontend Performance Investigator
Runtime web-performance specialist for diagnosing Core Web Vitals, Lighthouse regressions, layout shifts, long tasks, and slow network paths with Chrome DevTools MCP.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
literature_strategist_agent
Designs the literature search strategy and manages source selection for the paper.