← all publishers

szarkans

@szarkans source repo

Report this profile Claim this profile

• 6 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Ask · szarkans

   Put one question to several models at once — you, OpenAI Codex, and a cheap third via OpenCode — and show all the answers side by side. No judging, no consensus: three opinions, the user picks. Use for "ask everyone", "what do the other models think", "second opinion", "multi ask", or any open question where one model's answer is not enough.
   0
   installs
2. ▌
   Adhd · szarkans

   Divergent ideation across model families — the same brainstorm, but each cognitive frame is handed to a different model (Claude sub-agent, OpenAI Codex, a cheap third via OpenCode) so the ideas diverge by frame and by model priors at once. Use for open design questions, architecture and API shape, naming, schema choices, fuzzy bugs with no known root cause, or on "multi adhd", "brainstorm with everyone", "wide ideas from all models". Skip for lookups, syntax, and anything phrased as "quick", "standard" or "canonical".
   0
   installs
3. ▌
   Rune · szarkans

   RUNE
   0
   installs
4. ▌
   Setup · szarkans bundle

   Walks a user through connecting the judge models this plugin can use — Codex, OpenCode, OpenRouter (or any compatible endpoint: 9router, z.ai, Moonshot), Gemini — and through picking models, including "research current models for me". Use for "multi setup", "set up multi", "configure judges/reviewers/ backends", "connect 9router", "change/pick models", "onboarding", or whenever a probe shows missing backends and the user needs to know what to do about it.
   0
   installs
5. ▌
   Code Review · szarkans

   Code review by several models at once — Claude sub-agents, OpenAI Codex, and a cheap third reviewer via OpenCode — reconciled into one report. Reviews whatever is named: a diff, a branch, specific files, one function, a legacy module, a whole repo. Use for any review request, a second or third opinion, a cross-check before a PR, or "code-review", "multi", "consensus review".
   0
   installs
6. ▌
   Check If Done · szarkans

   Check whether the work is actually finished rather than finished-looking — what was promised versus what really runs. Several models compare the task against the code, and every completion claim has to survive a command that was actually executed. Use before calling something done, before a PR, at the end of a session, or on "is this done", "did I finish", "check if done", "what did we skip".
   0
   installs