Menü
Investigation workflow — gather sources, cross-check, summarize, cite. Use for literature review, tech comparisons, CVE research, and "how does X work" questions that need evidence.
Conduct advanced research in Artificial Intelligence and Mathematics, including the ability to generate and run automated tests or proofs.
Automatic test generation and execution. Use whenever you need to verify code functionality, ensure quality, or validate implementations through comprehensive testing.
Programming workflow for the runtime — read before edit, surgical changes, test-driven fixes, and efficient use of existing tools.
Core behavioral contract for the Ey-Code agent runtime. Use always — defines how the model coordinates reasoning and tool usage.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Ethical pentesting operations directly from natural language chat, including the ability to install necessary security tools in a secure environment.
| name | research-mode |
| description | Investigation workflow — gather sources, cross-check, summarize, cite. Use for literature review, tech comparisons, CVE research, and "how does X work" questions that need evidence. |
| when_to_use | - User asks "research X" or "compare A vs B". - User asks for CVEs, vulnerabilities, or security advisories on a component. - User asks to summarize a paper, repo, or long document. |
| license | MIT |
web_search, read_file on local refs, github_info for repos..reports/<topic>.md if the work is non-trivial.# <topic>
## Question
<one sentence>
## Findings
- <claim> — [source](url)
- <claim> — [source](url)
## Reading (interpretation)
<what this means for the user's actual need>
## Open questions
- <what's still unresolved>
web_search, github_info, read_file, semantic_search, search_references, add_reference.