semgrep-conventions

Name: semgrep-conventions
Availability: InStock
Author: KingInYellows

Standardize Semgrep integration conventions for API usage, token handling, and triage workflows.

Updated Jan 10, 2026

Search Tags:#security #validation #triage #semgrep #token-management #fencing #api-conventions

Ready to run

npx skills add https://github.com/KingInYellows/yellow-plugins --skill semgrep-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: semgrep-conventions
Source: https://github.com/KingInYellows/yellow-plugins/tree/main/plugins/yellow-semgrep/skills/semgrep-conventions
Command: npx skills add https://github.com/KingInYellows/yellow-plugins --skill semgrep-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides standardized conventions and safety guidelines for Semgrep-based integrations, ensuring consistent API usage, error handling, and triage workflows.

Core Features & Use Cases

API configuration templates for Semgrep integrations
Token handling and rate-limiting patterns
Consistent triage state mappings and data fencing for findings
Use Case: When integrating a new Semgrep-based plugin, apply these conventions to ensure predictable behavior and safety.

Quick Start

Refer to the conventions to implement a new Semgrep integration by following the API patterns and safety rules.

Frequently Asked Questions about semgrep-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are standard conventions for Semgrep API integration and token handling?▼

Standardized Semgrep integration conventions provide safe API token access patterns, JSON construction with jq, and consistent triage state mappings to ensure predictable behavior across plugins.

How do I implement safe data fencing for Semgrep finding triage?▼

Implement safe data fencing by applying consistent triage state mappings and validated API interaction patterns to securely mutate and isolate Semgrep findings during triage workflows.

Does this approach support standardized triage state mappings across multiple plugins?▼

Yes, standardized triage state mappings ensure consistent mutation and data fencing across API interactions, providing predictable behavior when integrating new Semgrep-based plugins.

What is the best way to handle rate limiting in Semgrep integrations?▼

The best way to handle rate limiting in Semgrep integrations is to apply standardized token handling and rate-limiting patterns that enforce safe API access and prevent quota exhaustion.

Why do I need validated JSON construction with jq for Semgrep API interactions?▼

Validated JSON construction with jq is required for Semgrep API interactions to safely structure data payloads, ensuring reliable token management and predictable error handling across integrations.