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.
npx agentmods add skills/ellmos-ai/bach/researchnpx skills add ellmos-ai/bach --skill researchgit clone --depth 1 https://github.com/ellmos-ai/bachWrote 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/skills/ellmos-ai/bach/research)<a href="https://agentmods.dev/skills/ellmos-ai/bach/research"><img src="https://agentmods.dev/badge/skills/ellmos-ai/bach/research.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 | $0.00041 | $0.00989 |
| Opus 5 | $0.00020 | $0.00495 |
| Sonnet 5 | $0.00008 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
research-agent 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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Agent
Version: 1.0.0 | Status: active | Erstellt: 2025-12-31 | Aktualisiert: 2026-01-22
Überblick
Der Research Agent ist spezialisiert auf wissenschaftliche Recherche, Literaturanalyse und evidenzbasierte Zusammenfassungen. Er orchestriert verschiedene KI-Tools und Datenbanken für umfassende Recherchen.
Fähigkeiten
1. Literaturrecherche
- Multi-Datenbank-Suche (PubMed, Consensus, Elicit)
- Fachspezifische Filterung
- Zeitraum-Einschränkungen
- Zitationsstil-Anpassung
2. Dokumentenanalyse
- PDF-Extraktion und Zusammenfassung
- Schlüsselkonzept-Identifikation
- Evidenz-Bewertung
- Quellenvergleich
3. Synthese
- Thematische Zusammenfassung
- Gap-Analyse
- Forschungsfragen-Entwicklung
- Hypothesen-Generierung
Integrierte Services
| Service | Funktion |
|---|---|
| prompt-manager | Optimierte Recherche-Prompts |
| scheduling | Forschungs-Deadlines |
| memory | Recherche-Ergebnisse speichern |
Externe Tools (KI-Center)
Primär
- Perplexity - Web-Recherche mit Quellen
- Consensus - Wissenschaftliche Papers
- NotebookLM - Dokument-Analyse
- Elicit - Literatur-Review
Sekundär
- Scite.ai - Zitations-Analyse
- Claude - Synthese und Analyse
- Gemini - Lange Dokumente
MCP-Verbindungen
connections/
├── connected_APIs/pubmed/ # PubMed API
├── connected_services/google_drive/ # Dokument-Speicher
└── connected_AIs/external/gemini/ # Deep Research Delegation
CLI-Befehle
# Agent starten (geplant)
bach research search "CRISPR autism therapy"
# Literatur-Review (geplant)
bach research review --topic "autism interventions" --years 5
# Dokument analysieren (geplant)
bach research analyze /path/to/paper.pdf
# Synthese erstellen (geplant)
bach research synthesize --sources ./papers/ --output report.md
Status: CLI-Handler noch nicht implementiert
Workflows
Schnell-Recherche (5 Min)
- Perplexity für Überblick
- Top 3-5 Quellen identifizieren
- Kurzzusammenfassung
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.
- 5d ago First seen · 187 lines · 41 tokens per session scan A 5ff781776f6d
research-agent is a skill published in the GitHub repository ellmos-ai/bach (7 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 989 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-31.
Other skills, from other repositories
memory-literary-analysis
Analyze a complete literary work into a structured Basic Memory knowledge graph. Covers schema design, entity seeding, chapter-by-chapter processing, cross-referencing, validation, and graph exploration.
bm-setup
Set up the Basic Memory plugin for this project — a short guided interview that configures the project mapping, seeds note schemas, learns or suggests placement conventions, and enables capture reflexes. Use when the user runs /basic-memory:bm-setup, says "set up basic memory", or asks to configure/bootstrap the…
memory-notes
How to write well-structured Basic Memory notes: frontmatter, observations with semantic categories, relations with wiki-links, and best practices for building a rich knowledge graph. Use when creating or improving notes.
memory-onboarding
Guide someone new to Basic Memory through designing and building a complete personal knowledge system — interview them about what they want to track, propose a structure, build it with schemas and instruction notes, teach them to use it, and set up their AI assistant to load it automatically. Use this skill whenever a…
infographics
Use when generating Basic Memory PR, changelog, release, or weekly images from Codex.
pr-review-loop
Enforce the Basic Machines GitHub PR review loop before merging. Use whenever Codex is preparing to merge, squash-merge, auto-merge, declare a PR ready, monitor Codex comments, address review feedback, or wait for Codex approval on a GitHub PR, especially when the user says "approved", "merge", "ship", "PR is ready"…