ModsCode / Claude Code Mods / Ranking / shell-mode
shell-mode
用 /shell-mode 切换 Bash 模式,连续执行命令并显示颜色,退出后将输出保留在 CLI 中
What it does
- Draws a pane, toasts
- Adds /shell-mode
- Hooks command.describe, session.end, session.start, ui.close and 1 more
- Starts processes
Good points
- No network calls
- Written in TypeScript
- Handles errors
Code to start from
A starter ModsCode writes from the drawing it read, and the mod's own lines that draw, where there are any.
Starter (register.tsx)
import type { Register } from 'claude-code'
// Drawn like shell-mode by h1048576 (pane, toast), as ModsCode read it from the mod's code:
// https://modscode.com/claude-mods/mods/h1048576-shell-mode/
// Written by ModsCode from that reading, not copied from the mod: use it as you like.
// Each value below stands for one the mod works out at run time; put in your own.
export const register: Register = on => {
// the pane: open it with $.ui.open({ id: 'my-pane', title: "Shell Mode" })
on('ui.render', { component: 'Pane', requestId: 'my-pane' }, async ($, e) => {
const { Box, Text, Input } = $.ui.resolve(e)
const piece = '…'
const piece2 = '…'
const piece3 = '…'
const piece4 = '…'
const piece5 = '…'
const piece6 = '…'
const piece7 = '…'
const piece8 = '…'
const piece9 = '…'
const piece10 = '…'
const piece11 = '…'
const piece12 = '…'
const piece13 = '…'
const piece14 = '…'
const piece15 = '…'
const piece16 = '…'
const piece17 = '…'
const piece18 = '…'
const piece19 = '…'
const piece20 = '…'
const piece21 = '…'
const piece22 = '…'
const piece23 = '…'
const piece24 = '…'
const piece25 = '…'
const piece26 = '…'
const piece27 = '…'
return (
<Box flexDirection="column">
<Box flexDirection="column">
<Text wrap="wrap">
<Text>
{piece}
</Text>
<Text>
{piece2}
</Text>
<Text>
{piece3}
</Text>
<Text>
{piece4}
</Text>
<Text>
{piece5}
</Text>
<Text>
{piece6}
</Text>
<Text>
{piece7}
</Text>
<Text>
{piece8}
</Text>
<Text>
{piece9}
</Text>
</Text>
<Text wrap="wrap">
<Text>
{piece10}
</Text>
<Text>
{piece11}
</Text>
<Text>
{piece12}
</Text>
<Text>
{piece13}
</Text>
<Text>
{piece14}
</Text>
<Text>
{piece15}
</Text>
<Text>
{piece16}
</Text>
<Text>
{piece17}
</Text>
<Text>
{piece18}
</Text>
</Text>
<Text wrap="wrap">
<Text>
{piece19}
</Text>
<Text>
{piece20}
</Text>
<Text>
{piece21}
</Text>
<Text>
{piece22}
</Text>
<Text>
{piece23}
</Text>
<Text>
{piece24}
</Text>
<Text>
{piece25}
</Text>
<Text>
{piece26}
</Text>
<Text>
{piece27}
</Text>
</Text>
</Box>
<Box flexDirection="row">
<Text>
{"$ "}
</Text>
<Input value="" autoFocus submitLabel="" />
</Box>
</Box>
)
})
on('session.start', async ($, e, next) => {
const message = '…'
await $.ui.toast(`无法保存 Shell 输出,控制台继续保留:${message}`)
await $.ui.toast(`用法:/shell-mode 切换 Bash 模式;on 明确开启,off 或 exit 退出。`)
return next(e)
})
}
The mod's own code
Its licence text was not found at the commit read, so only the places in the source are linked.
How to build this: Pane (panel), Add a slash command
What its code calls
runs programswrites filesenv varscalls tools
What its code shows
Read from the source at commit 5cf7bfcf894b on 2026-10-11. The first group decides whether a mod is listed; the rest is for you to weigh. A later commit is not read until the next crawl.
| Decides the listing: code you can check | |
|---|---|
| Entry read | Every module hooks/hooks.json names was read.shell-mode/hooks/register.ts |
| Parses | Every file parses as TypeScript or JavaScript.2 files parsed |
| All its code is in the mod | Every import is a file of the mod or the engine's own module; no packages, no require.all its code is in the mod |
| Readable | No minified lines, no eval or new Function, no import of a computed path, no encoded blobs.no minified code, no eval, no encoded blobs |
| Calls in the open | Network and programs are reached as $.http.fetch and $.process.run in place, never passed around.every call outside goes through $ in the open |
| For you to weigh before installing | |
| Where it draws | The terminal, the desktop app, both, or nothing (hooks only: a guard or a prompt rewriter), as its code says. Shown, never a reason to leave a mod out.draws in the terminal and the desktop app, the same in both |
| Install line | Whether its repository's own .claude-plugin/marketplace.json lists it, so it installs from that marketplace with the lines on its page.its repository's .claude-plugin/marketplace.json does not list it: no marketplace line to give; the page shows how to try the commit read |
| Programs on Windows | Whether every program it starts through $.process exists on Windows (tail, date, open, osascript, /usr/… do not).runs no program a Windows PC lacks |
| Network | Whether every fetch names its https host in the code.no network |
| Programs | Whether every program it starts is named in the code and is not a shell, an interpreter or a network tool.shell-mode/hooks/register.ts:150 a program named at run time |
| Reads and sends | Whether it both reads something of yours (files, environment variables, the transcript, settings) and reaches outside (the network, an MCP server, another session, telemetry).reads environment variables, files, but reaches nothing outside |
| Keys in the source | Whether the source holds what looks like an API key or a private key.no keys in the source |
| Licence | An open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD, CC0) with its text lets ModsCode show its code; otherwise the code is linked.no licence |
| Settings hooks | Hooks declared in hooks/hooks.json or plugin.json beside the module: a command (a shell when it has no args), an HTTP request, an MCP tool or a model prompt at an event. They run outside $.no settings hooks: its function hooks alone |
| Servers it ships | MCP servers (a program, or a URL; a headersHelper is a shell command; a .mcpb bundle is unpacked at run time), LSP servers, monitors (a shell command for the whole session) and bin/ (on the PATH of the Bash tool).ships no MCP or LSP server, no monitor, no bin/ |
| Skills, commands, agents | What its Markdown declares beyond text: allowed-tools granted for the turn, hooks added when a skill is invoked, a command run before Claude reads the skill.no skills, commands, agents or workflows |
| Tools and MCP | Whether every tool it calls through $.tool.call and $.mcp.call is named in the code, and none is a shell (Bash through the tool runs a shell without $.process).command.run: /? |
| Asks of the model | Completions it runs ($.model.complete, fork, classify), subagents it spawns, prompts it submits as you, and the tools, commands and agents it adds.adds command shell-mode, adds command ? |
| Events it hooks | By what a hook there can do: gates (refuse a tool call, a prompt, a setting, another plugin), shapes (what the model reads: the system prompt, tool descriptions, each request), reads (your input, the events of the settings hooks, every event with *), and the rest.gates: command.run (shell-mode) · shapes: command.describe · reads: ui.input · also: session.start, ui.render (CommandOutput, UserMessage, Pane), ui.close, session.end |
| Reads, by name | The environment variables and files it names, and whether it reads the transcript, settings.json, the prompt box or the mouse selection.env: LOCALAPPDATA, USERPROFILE, CLAUDE_CODE_GIT_BASH_PATH, ProgramFiles, ProgramW6432; files: a path computed at run time |
| Writes, by name | The files and environment variables it names, and whether it changes settings, the prompt box, the clipboard, the conversation (a row the model reads) or another session.files: a path computed at run time |
This is a reading of the code text, not a security review: it does not run the mod, and it cannot see what a program the mod starts does. The check before installing is yours. How mods are chosen
Install it
Check it yourself before you install it. Mods run unsandboxed, with your permissions, and ModsCode does not vouch for what this code does. Read its code (or run claude plugin validate . in its folder), weigh what it reaches, and install the commit you read.
Its repository's .claude-plugin/marketplace.json does not list it, so there is no marketplace line to give.
Try the commit ModsCode read
No marketplace needed. In a terminal, clone the repository, check out the commit read, validate the mod, and load it for one session:
git clone https://github.com/h1048576/claude-modsgit -C claude-mods checkout 5cf7bfcf894b3f3000d6ffb1d3c9ef7aa9030639claude plugin validate claude-mods/shell-modeclaude --plugin-dir claude-mods/shell-modeThe validate line lists the events the mod hooks and what it asks Claude Code to do, without running it. The last line loads the mod for this session only and writes nothing to your settings. If the author has rewritten history, the commit may no longer exist.
Ask Claude about it
With the ModsCode connector added, Claude can read this mod's code and what it reaches, and build on them. Ask it like this:
Read the ModsCode mod "h1048576-shell-mode" with its code and make me one like itSearch them from Claude: the MCP connector
Similar mods
- code-modernizationAnthropic★ 37,653
- lcu-approveLCU★ 894
- ai-maestro-secrets23blocks-OS★ 817
- filetreeKurt Buhler★ 131
- great-ctoAlexander Velikiy★ 103
- hopeSaad Shahd★ 35
More from this repository
Badge for your README
If this is your mod, paste this into your README. It links to this page.
[](https://modscode.com/claude-mods/mods/h1048576-shell-mode/)