Skip to content
anyai.fyi

remove-guardian-developer-semgrep-rule

Skill from semgrep/mcp-marketplace

Other No risky patterns found curated mcp

Install

npx skills add semgrep/mcp-marketplace --skill remove-guardian-developer-semgrep-rule

Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.

As a Claude Code plugin

/plugin marketplace add anthropics/claude-plugins-official /plugin install semgrep@semgrep-marketplace

This skill is part of the plugin “semgrep”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.

What does the remove-guardian-developer-semgrep-rule skill do?

Remove a custom Semgrep rule from Guardian — list what is installed, work out which file holds the rule, and delete or edit it out of the user or repo rules directory. Use when someone wants Guardian to stop flagging something, asks to remove, delete or disable a custom rule, or wants to clear room under the rule limit.

Description from the SKILL.md in the source repository.

Questions about remove-guardian-developer-semgrep-rule

What does the remove-guardian-developer-semgrep-rule skill do?

Remove a custom Semgrep rule from Guardian — list what is installed, work out which file holds the rule, and delete or edit it out of the user or repo rules directory. Use when someone wants Guardian to stop flagging something, asks to remove, delete or disable a custom rule, or wants to clear room under the rule limit.

How do I install remove-guardian-developer-semgrep-rule?

In a terminal: npx skills add semgrep/mcp-marketplace --skill remove-guardian-developer-semgrep-rule. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.

Which agents can use remove-guardian-developer-semgrep-rule?

Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.

Is remove-guardian-developer-semgrep-rule safe to use?

Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.

More skills from semgrep/mcp-marketplace

add-and-validate-guardian-developer-semgrep-rule
semgrep/mcp-marketplace

write a custom semgrep rule with the user, add it to guardian in either user or repo scope, and prove it fires by writing a file that should trip it. use when someone wants guardian to catch something it currently misses, asks to write or add a semgrep rule, or wants a project convention enforced on the code claude writes.

Writing & Marketing curated
No risky patterns found
install-mfw
semgrep/mcp-marketplace

Install the mfw (Semgrep Malware Firewall) CLI via the curl|sh installer and walk the user through setup — trust store, PATH shims, shell integration, and the background daemon — asking questions at real decision points. Detects when the user's shell rc files are *managed* (symlinked into nix / home-manager / chezmoi / GNU stow / a dotfiles git repo) and, instead of clobbering them, adds mfw's source line to the right source-of-truth. Use when the user wants to install, set up, or onboard mfw on this machine.

Development curated
Risky patterns
recommend-guardian-policy-rules
semgrep/mcp-marketplace

Recommend Semgrep rules to add to the organization's Guardian policy for a repository — pull the rules Guardian runs now, gather candidates from the repo's existing findings and the org's custom rules, rank them for Guardian, let the user pick, and turn the picks on through the Semgrep MCP. Use when someone wants Guardian to catch more, asks which rules Guardian should run, or wants to tune or customize the Guardian policy for a repo.

Other curated
No risky patterns found
reconnect
semgrep/mcp-marketplace

Re-check Semgrep Guardian's connection and recover it — verify the credential live, and log in again if it is expired. Use when Guardian reported that it timed out checking credentials or could not reach Semgrep, when scans seem not to be running, or when the user asks to reconnect Guardian.

Other curated
No risky patterns found

Related skills in Other