echoVic

179 mods in 2 plugins, 4 repositories, 1.2k stars between them.

echoVic/blade-code

Skill Claude CodeCodex

A tool platform that defines, registers, authorises, and runs the actions an agent can take, such as file edits, shell commands, browser work, and Git worktrees.

not rated 181 3d ago A SkillSpector: pass 177 tokens original MIT

echoVic/blade-code

Skill Claude CodeCodex

A browser-automation component that gives each session an isolated Chromium browser for navigating pages, inspecting them, interacting with them, and taking diagnostic screenshots.

not rated 181 3d ago A SkillSpector: pass 162 tokens original MIT

echoVic/blade-code

Skill Claude CodeCodex

Shell and Git worktree support for running commands, managing long-lived processes, and giving sessions isolated working directories. A Git worktree is a separate checkout linked to the same repository.

not rated 181 3d ago A SkillSpector: pass 164 tokens original MIT

echoVic/blade-code

Skill Claude CodeCodex

A common contract and registry for built-in tools, MCP tools, and agent-facing tools. It validates tool parameters, decides which tools are visible to a model, and stores session artifacts privately.

not rated 181 3d ago A 156 tokens copy · 86% MIT

echoVic/blade-code

Skill Claude Code

The controlled path that turns a tool request into an actual side effect, such as editing files or running a command. It coordinates validation, permissions, hooks, approvals, concurrency, file locks, safe retries, verification, and result delivery.

not rated 181 3d ago A 165 tokens copy · 88% MIT

echoVic/blade-code

Skill Claude CodeCodex

A shared foundation for configuration, workspace trust, session resources, API contracts, tool access, capacity limits, output flow, and shutdown across the command line, web app, agents, and extensions.

not rated 181 3d ago A 152 tokens copy · 80% MIT

echoVic/blade-code

Skill Claude Code

A resource-management layer that limits concurrent sessions, tasks, tools, providers, and browser work. It also controls streamed output and cleans up processes during cancellation or shutdown.

not rated 181 3d ago A 177 tokens copy · 80% MIT

echoVic/blade-code

Skill Claude CodeCodex

A configuration system that combines user, project, local, and per-call settings, then saves each field to the correct scope and file. It can rebuild settings for a particular source project.

not rated 181 3d ago A SkillSpector: pass 143 tokens original MIT

echoVic/blade-code

Skill Claude Code

A permission and workspace-trust system for deciding whether tools, hooks, browser actions, project settings, and sensitive paths may be used. It supports allow, ask, and deny decisions and identifies trusted project sources.

not rated 181 3d ago A 147 tokens copy · 81% MIT

echoVic/blade-code

Skill Claude CodeCodex

Shared runtime state and diagnostics for the command line, server, web app, agents, tools, and extensions. It tracks working directories, project roots, session IDs, logs, environment details, and registered projects.

not rated 181 3d ago A 198 tokens copy · 89% MIT

echoVic/blade-code

Skill Claude CodeCodex

Shared request and response definitions for the server and web app, with runtime checks for incoming data and cleaned JSON schemas for tools. TypeBox is the library used to describe these data shapes.

not rated 181 3d ago A SkillSpector: pass 149 tokens original MIT

echoVic/blade-code

Skill Claude CodeCodex

A workspace resource layer that gives each agent session its own fixed view of models, communication styles, hooks, and project instructions. It keeps the project that owns a resource separate from the working directory where files are edited.

not rated 181 3d ago A 141 tokens copy · 86% MIT

mermaid-chart-mcp

137

echoVic/mermaid-chart-mcp

MCP server Claude CodeCodexCursor +2

MCP server "mermaid-chart-mcp" as configured in echoVic/mermaid-chart-mcp. Runs locally from the mermaid-chart-mcp npm package.

not rated 1 1y ago A tokens not measured

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: