loop-solution-council

loop-solution-council is a command for Claude Code, Cursor from Oriolshhh/runware-image-mcp. It costs 0 tokens per session (765 once invoked), scanned A, original, MIT.

A structured team-style workflow for investigating a software failure through discovery, specialist review, experiments, a fix, and verification.

In plain words
What is it for?
Use it to reproduce a bug, narrow down its cause, test one change at a time, add a regression test, and run the original and related checks.
Why use it?
It replaces guesswork with a reproducible failure, ranked explanations, and evidence for the chosen fix.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md). Also seen: mentions subagents.

Good fit Use it to reproduce a bug, narrow down its cause, test one change at a time, add a regression test, and run the original and related checks.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/oriolshhh/runware-image-mcp/loop-solution-council
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.

Clone the repo
git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for loop-solution-council

README.md
[![agentmods](https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/loop-solution-council/github.svg)](https://agentmods.dev/commands/oriolshhh/runware-image-mcp/loop-solution-council)
Your own site
<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/loop-solution-council"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/loop-solution-council/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for loop-solution-council

Your own site · 80×15
<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/loop-solution-council"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/loop-solution-council.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 765 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00765
Opus 5 $0.00000 $0.00382
Sonnet 5 $0.00000 $0.00153
Haiku 4.5 $0.00000 $0.00076

Measured 7d ago against content hash b60abc01615f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

loop-solution-council 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 7d 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.

.cursor/commands/loop-solution-council.md · 91 lines

What it actually says

/loop-solution-council — Discovery, specialist review, one challenge round, and chair synthesis.

Follow this ordered workflow. Respect every human-approval gate and stop when instructed.

# `mode: parallel-when-supported` means: run independently in parallel only if the
# platform provides isolated subagents; otherwise run sequentially or as simulated
# role passes, and never claim independence the target cannot guarantee.
name: solution-council
description: Produce an evidence-backed implementation recommendation through bounded specialist review.
max_iterations: 1
steps:
  - id: discovery
    name: discovery
    agent: product-discovery
    output: decision-brief
    instruction: >-
      Reuse .agent/context/ via context-discovery, inspect repository evidence,
      and produce a decision brief (facts, assumptions, preferences, blockers).
      Build one task context capsule for every specialist delegation.
      Ask at most 3 (max 5) grouped, decision-changing questions; otherwise state
      defaults and continue.

  - id: route
    name: route
    agent: council-router
    input: decision-brief
    output: selected-specialists
    instruction: >-
      Select the smallest relevant specialist set (always architecture and
      product; add others only on evidence), select each role's model tier via
      model-routing, and justify both choices. Skip the full council for trivial,
      low-risk changes. Keep chair synthesis heavy/high.

  - id: independent-review
    name: independent-review
    mode: parallel-when-supported
    agents_from: selected-specialists
    input: decision-brief
    output: specialist-reports
    instruction: >-
      Each selected specialist produces a first-pass report from the brief without
      seeing the others' reports. Use the strongest isolation the platform supports
      (parallel subagents, else sequential subagents, else simulated role passes)
      and record which mode was used.

  - id: challenge
    name: challenge
    mode: parallel-when-supported
    agents_from: selected-specialists
    input:
      - decision-brief
      - specialist-reports
    max_rounds: 1
    output: rebuttals
    instruction: >-
      Exactly one bounded round. The devil's advocate and selected specialists
      challenge the leading proposal with evidence-based objections, unsupported
      assumptions, and premature-consensus checks. No further rounds.

  - id: synthesis
    name: synthesis
    agent: council-chair
    input:
      - decision-brief
      - specialist-reports
      - rebuttals
    output: decision-record
    instruction: >-
      Synthesize (do not vote) into one decision record: recommended path,
      confidence with deliberation mode, rejected alternatives, risks, preserved
      dissent, and unresolved questions. Cite only evidence present in the reports.

  - id: approve
    name: approve
    gate: human-approval
    instruction: >-
      Stop and present the decision record for explicit human approval. Do not
      implement production code.

  - id: handoff
    name: handoff
    command: /spec
    instruction: >-
      Only after approval, hand off to /spec to enter spec-to-implementation.

Apply context-discovery before broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read .agent/context/routing.md, load only relevant summaries, and verify critical claims against source.

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. 7d ago First seen · 91 lines · 0 tokens per session scan A b60abc01615f

Subscribe to this mod's changes

loop-solution-council is a command published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 765 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-09-03.