feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command
Add /ultraresearch-local for structured research combining local codebase analysis with external knowledge via parallel agent swarms. Produces research briefs with triangulation, confidence ratings, and source quality assessment. New command: /ultraresearch-local with modes --quick, --local, --external, --fg. New agents: research-orchestrator (opus), docs-researcher, community-researcher, security-researcher, contrarian-researcher, gemini-bridge (all sonnet). New template: research-brief-template.md. Integration: --research flag in /ultraplan-local accepts pre-built research briefs (up to 3), enriches the interview and exploration phases. Planning orchestrator cross-references brief findings during synthesis. Design principle: Context Engineering — right information to right agent at right time. Research briefs are structured artifacts in the pipeline: ultraresearch → brief → ultraplan --research → plan → ultraexecute. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
commit
f153f969a0
196 changed files with 43854 additions and 0 deletions
54
commands/mcp-inspect.md
Normal file
54
commands/mcp-inspect.md
Normal file
|
|
@ -0,0 +1,54 @@
|
|||
---
|
||||
name: security:mcp-inspect
|
||||
description: Connect to running MCP servers and scan live tool descriptions for injection, shadowing, and drift
|
||||
allowed-tools: Bash, Read
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
# /security mcp-inspect [path]
|
||||
|
||||
Live MCP runtime inspection — connects to each configured MCP stdio server via JSON-RPC 2.0, fetches tool/prompt/resource lists, and scans descriptions for injection patterns and tool shadowing.
|
||||
|
||||
## Step 1: Run Scanner
|
||||
|
||||
Determine plugin root (parent of this `commands/` folder) and target path from `$ARGUMENTS` (default `.`).
|
||||
|
||||
```bash
|
||||
node <plugin-root>/scanners/mcp-live-inspect.mjs "<target>"
|
||||
```
|
||||
|
||||
Parse stdout as JSON. If exit code is non-zero and no JSON output, show the error and STOP.
|
||||
|
||||
## Step 2: Report
|
||||
|
||||
Display:
|
||||
|
||||
```
|
||||
## MCP Live Inspection: <VERDICT>
|
||||
|
||||
**Servers:** <discovered> discovered | <contacted> contacted | <timed_out> timed out | <skipped_sse> SSE skipped | <failed> failed
|
||||
|
||||
### Server Details
|
||||
| Server | Status | Tools | Prompts | Resources | Time |
|
||||
```
|
||||
|
||||
For each finding (sorted critical → info):
|
||||
|
||||
```
|
||||
### Findings (<count>)
|
||||
|
||||
| # | Severity | Title | OWASP | Recommendation |
|
||||
```
|
||||
|
||||
If zero findings: "No injection, shadowing, or drift detected across N servers."
|
||||
|
||||
## Step 3: Advisory
|
||||
|
||||
- If `servers_timed_out > 0`: "N servers timed out (10s). Ensure they can start independently — check command, env vars, and args."
|
||||
- If `servers_skipped_sse > 0`: "N SSE servers skipped — live inspection requires stdio transport."
|
||||
- If `servers_failed > 0`: "N servers failed to start. Verify the command path exists and is executable."
|
||||
- If `servers_discovered == 0`: "No MCP servers found in config locations. Check .mcp.json, .claude/settings.json, or ~/.claude/settings.json."
|
||||
|
||||
## Step 4: Combined Use
|
||||
|
||||
Mention: "For combined static + live analysis, use `/security mcp-audit --live`."
|
||||
Loading…
Add table
Add a link
Reference in a new issue