init

A setup command for eyeroll, a tool that analyzes videos and screenshots to help with software bugs and features. It selects an AI service, installs needed packages, saves its settings, and creates notes about the project.

In plain words
What is it for?
Use it to prepare a project for eyeroll analysis and generate a file describing the codebase for later bug investigations.
Why use it?
It removes the manual work of installing eyeroll, configuring an AI service, and gathering basic project information before using it.

Command

Install

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.

agentmods
npx agentmods add commands/mnvsk97/eyeroll/init
Clone the repo
git clone --depth 1 https://github.com/mnvsk97/eyeroll
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 514 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00514
Opus 5 $0.00000 $0.00257
Sonnet 5 $0.00000 $0.00103
Haiku 4.5 $0.00000 $0.00051

Measured 3d ago against content hash 2d1fb41e26a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

init 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 3d 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.

docs-site/docs/commands/init.md · 62 lines

What it actually says

/eyeroll:init

Set up eyeroll for the current project -- pick a backend, install dependencies, and generate codebase context.

Usage

/eyeroll:init

No arguments needed.

What it does

Step 1: Check installation

Checks if eyeroll CLI is installed. If not, asks which backend you want and installs the appropriate package:

Choice Install command
Gemini pip install eyeroll[gemini,download]
TwelveLabs pip install eyeroll[twelvelabs]
OpenAI / OpenRouter / Groq / Grok / Cerebras / openai-compat pip install eyeroll[openai,download]
Ollama pip install eyeroll[download]

Step 2: Configure backend

Runs eyeroll init interactively:

  • Prompts for backend choice (Gemini, TwelveLabs, OpenAI, Ollama, OpenRouter, Groq, Grok, Cerebras, openai-compat)
  • For Gemini/TwelveLabs/OpenAI: prompts for API key and validates the local SDK setup
  • For Ollama: verifies Ollama is running (or starts it)
  • Saves configuration to ~/.eyeroll/.env

Step 3: Generate codebase context

Explores the project and writes .eyeroll/context.md:

  1. Reads CLAUDE.md, README.md, pyproject.toml or package.json
  2. Checks git log --oneline -10 and current branch
  3. Lists root and key source directories
  4. Skims 2-3 key source files

The resulting file is a short summary (under 80 lines) that eyeroll uses to ground its analysis in real file paths.

What gets created

File Location Purpose
.env ~/.eyeroll/.env Backend preference and API key
context.md .eyeroll/context.md Project summary for grounded analysis

When to re-run

Re-run /eyeroll:init when:

  • You want to switch backends
  • Your API key has changed
  • The project structure has changed significantly (major refactor, new directories)

The codebase context file is what makes the difference between vague guesses and precise file references in eyeroll reports.

Changes

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.

  1. 3d ago First seen · 62 lines · 0 tokens per session scan A 2d1fb41e26a2

Subscribe to this mod's changes

init is a command published in the GitHub repository mnvsk97/eyeroll (17 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 514 tokens. 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.