mobb-vulnerabilities-fixer
Scan, fix, and remediate security vulnerabilities in a local code repository using Mobb MCP/CLI. Use when the user asks to scan for vulnerabilities, run a security check, auto-fix issues, remediate findings, or apply Mobb fixes (e.g., \"scan this repo\", \"fix security issues\", \"remediate vulnerabilities\", \"run Mobb on my changes\").
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/jonathansantilli/mobb-vulnerabilities-fixerMobb Vulnerabilities Fixer
Overview
Use Mobb MCP scan-and-fix behavior to identify security issues in a local repo and apply the generated patches. Follow the MCP workflow exactly, including file selection, pagination, and rescan rules.
Workflows
Scan and Fix (default)
-
Confirm target repository path. Use an absolute path to the repository root. Reject paths with traversal patterns. If the user gives
.and a workspace root is known, use it. -
Ensure Mobb authentication is available. Prefer
API_KEYin the environment. If missing or invalid, inform the user a browser window will open for Mobb login and authorization, then proceed once authenticated. If the user has no account, instruct them to create one and generate an API key. Seereferences/mobb-auth.md. -
Require MCP to be already running. Do not install or launch MCP yourself. Ask the user to start the Mobb MCP server on their machine using their approved process and confirm it is running before you proceed.
-
Execute MCP scan-and-fix. Invoke the MCP tool
scan_and_fix_vulnerabilitieswith the repository path. Use optional parameters only when the user explicitly asks.
Required parameter:
path: absolute path to the repository root
Optional parameters:
offset: pagination offset for additional fixeslimit: maximum number of fixes to return (default is 3)maxFiles: scan up to N recently changed files (default is 10); setting this triggers a fresh scanrescan: force a full rescan; only when user explicitly asksscanRecentlyChangedFiles: when true and no git changes are found, scan recently changed files from history
-
Apply returned fixes only with explicit user consent. If the tool returns patches, summarize what will change and ask the user to confirm before applying. Apply patches exactly as provided, modify nothing else, and explain after applying. If a patch cannot be applied, report the exact conflict and continue with others the user approved.
-
Never auto-rescan or auto-page. Do not rescan or fetch additional pages of fixes unless the user explicitly asks. If more fixes are available, inform the user how to request the next page.
Fetch Available Fixes (summary only)
Use when the user wants a summary of available fixes without uploading/scanning or applying patches.
Call fetch_available_fixes with:
path: absolute path to the repo rootoffsetandlimit: optional paginationfileFilter: optional list of relative paths to filter fixesfetchFixesFromAnyFile: optional boolean to fetch fixes for all files
fileFilter and fetchFixesFromAnyFile are mutually exclusive. If neither is provided, the tool filters to files with git status changes.
Check for New Available Fixes (monitoring)
Call check_for_new_available_fixes once at the end of a session after edits/tests, or when the user explicitly asks to check for fresh fixes.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-jonathansantilli-mobb-vulnerabilities-fixer": {
"enabled": true,
"auto_update": true
}
}
}