{ "name": "semgrep-rule-variant-creator", "version": "1.0.0", "description": "Creates language variants of existing Semgrep rules with proper applicability analysis and test-driven validation", "author": { "name": "Maciej Domanski", "email": "opensource@trailofbits.com" } }
Claude Plugin
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules with proper applicability analysis and test-driven validation
Editor's Note
Creates language variants of existing Semgrep rules with proper applicability analysis and test-driven validation
Plugin Overview
This item is backed by a plugin manifest rather than a `SKILL.md` file, so the most useful fields are surfaced here first.
Plugin Name
semgrep-rule-variant-creator
Version
1.0.0
Author
Maciej Domanski (opensource@trailofbits.com)
Manifest Description
Creates language variants of existing Semgrep rules with proper applicability analysis and test-driven validation
Raw Manifest
The structured plugin fields above are derived from the same upstream manifest shown below.
Related Items
Claude Plugin
trailmark
Builds multi-language source code graphs for security analysis: call graphs, attack surface mapping, blast radius, taint propagation, complexity hotspots, and entry point enumeration. Generates Mermaid diagrams (call graphs, class hierarchies, dependency maps, heatmaps). Compares code graph snapshots for structural diff and evolution analysis. Runs graph-informed mutation testing triage (genotoxic). Generates mutation-driven test vectors (vector-forge). Extracts crypto protocol message flows and converts Mermaid diagrams to ProVerif models. Projects SARIF and weAudit findings onto code graphs. Use when analyzing call paths, mapping attack surface, visualizing code architecture, triaging survived mutants, generating cryptographic test vectors, diagramming crypto protocols, formally verifying protocols, or augmenting audits with static analysis findings.
Claude Plugin
yara-authoring
YARA-X detection rule authoring with linting and quality analysis
Claude Plugin
code-quality
Comprehensive code analysis, refactoring automation, and clean code enforcement.
Claude Plugin
experiment-tracker
PROACTIVELY use this agent when experiments are started, modified, or when results need analysis. This agent specializes in tracking A/B tests, feature experiments, and iterative improvements within the 6-day development cycle. Should be triggered automatically when experimental code paths or feature flags are introduced. Examples:\n\n<example>\nContext: When implementing feature flags or A/B test variants\nuser: "Add a feature flag to test the new onboarding flow"\nassistant: "I've implemented the feature flag for the onboarding flow A/B test. Let me use the experiment-tracker agent to properly document this experiment and set up tracking."\n<commentary>\nEvery feature flag represents an experiment that needs proper tracking and success metrics.\n</commentary>\n</example>\n\n<example>\nContext: After deploying experimental features\nuser: "The new viral sharing feature is now live for 10% of users"\nassistant: "Great! The viral sharing feature is deployed. I'll use the experiment-tracker agent to monitor its performance and document initial results."\n<commentary>\nLive experiments need immediate tracking setup to capture valuable data from the start.\n</commentary>\n</example>\n\n<example>\nContext: When reaching experiment milestones\nuser: "It's been a week since we launched the TikTok integration test"\nassistant: "Perfect timing for analysis. Let me use the experiment-tracker agent to compile the week-one results and determine if we should expand the test."\n<commentary>\nRegular experiment checkpoints ensure data-driven decisions about feature rollouts.\n</commentary>\n</example>\n\n<example>\nContext: Before making product decisions\nuser: "Should we keep the AI avatar feature or remove it?"\nassistant: "Let me analyze the experiment data to inform this decision. I'll use the experiment-tracker agent to review all metrics and user feedback for the AI avatar feature test."\n<commentary>\nProduct decisions should be backed by experiment data, not gut feelings.\n</commentary>\n</example>
