Skip to content
Agentmart
Submit a tool

input-mode-detection

Defines four input modes (analysis-only, plan-only, both, neither) and the corresponding behaviour for each — used by programmer agents to determine how to…

Skill by MoltenRuby

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/moltenruby-input-mode-detection

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Defines four input modes (analysis-only, plan-only, both, neither) and the corresponding behaviour for each — used by programmer agents to determine how to handle incoming context before writing any code

Use cases: writing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/input-mode-detection

What's inside

Skill name
input-mode-detection
Description
Defines four input modes (analysis-only, plan-only, both, neither) and the corresponding behaviour for each — used by programmer agents to determine how to handle incoming context before writing any code
License
MIT
Compatibility
opencode
Instructions
25 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

## Input modes

Your behaviour depends on what input you receive. Determine the mode from the user message before doing anything else.

### Mode 1 — Analysis provided, no plan

An analysis describes findings, constraints, or a diagnosis. It does not prescribe steps.
Your job: derive a concrete implementation plan from the analysis, then execute it.
Apply your own judgement to fill gaps. If the analysis is ambiguous on a critical point, ask one clarifying question before proceeding.

### Mode 2 — Plan provided, no analysis

A plan prescribes steps to implement. Follow it rigorously.
Apply your own judgement to improve the plan where you see clear gains. Follow the deviation rules.

### Mode 3 — Both analysis and plan provided

The analysis informs; the plan prescribes. Treat the plan as the primary directive.
Use the analysis to fill in detail the plan omits. Apply your own judgement to improve. Follow the deviation rules.

### Mode 4 — Neither provided (direct instructions)

The user message is the specification. Treat it as you would a plan: follow it rigorously, apply your own judgement to improve, and follow the deviation rules.

From MoltenRuby/MrSmith, MIT.

More from MoltenRuby/MrSmith

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Mar 21, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/MoltenRuby/MrSmith
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from MoltenRuby

Cite this page

input-mode-detection skill. Agent Mart. https://agentmart.dev/skills/moltenruby-input-mode-detection (last updated 2026-10-24)