Find application-specific vulnerabilities with whole-program static taint analysis and write rules and dependency models for future scans
175 on GitHubby Seqrav0.3.0Apache-2.0updated 10 days agosecurity
/
Plugin appsec-workflow from marketplace opentaint in seqra/opentaint. Commands read from the repo's manifest — 10 days ago.
What it installs
Skills (16)
analyze-external-methods
Analyze an OpenTaint scan's dropped external methods and decide which of them are propagators and optionally sinks. Use when a dropped-external-methods.yaml needs classification for dropped method type
analyze-findings
Triage OpenTaint findings statically. Use when scan findings need a TP/FP verdict
appsec-agent
Run an end-to-end OpenTaint application-security analysis while owning the long project build and scans and delegating each other pipeline stage. Use when the user asks to find vulnerabilities, or scan an application for security issues
assemble-lib-rules
Connect the shared untrusted-data source group to new reusable OpenTaint sink groups. Use to wire new sink tags into security joins
build-project
Build a target project into an opentaint project model. Use whenever a fresh opentaint project model needed
create-dataflow-model
Model a method's taint propagation as code-based dataflow model and refine it against a test project until the sample passes. Use for a dropped method that requires code-based model
create-pass-through-model
Model a method's taint propagation as a passThrough model. Use for a dropped method whose propagation is simple copying
create-rule
Author and verify an OpenTaint rule. Use whenever a rule creation is needed
create-test-project
Create an OpenTaint test project with positive/negative samples for verifying a rule or model. Use when a rule or model needs a test project to check against
debug-rule
Debug a rule or model that behaves unexpectedly by tracing where taint is dropped. Use when its samples won't pass after repeated attempts, or it passes tests but is wrong on a real scan
discover-attack-surface
Classify project-used dependency members and record taint sources as rule-authoring units. Use for the source-discovery depth pass
generate-poc
Reproduce a true-positive finding against the running application. Use when a finding needs dynamic confirmation
orchestrate-stage
Run one stage of the OpenTaint pipeline by coordinating leaf subagents and deterministic joins. Use when a separate OpenTaint pipeline stage needs to be executed
report-analyzer-issue
Write a self-contained OpenTaint engine-issue report from an analysis diagnosis or a full-scan failure. Use when an engine-side issue needs a report
run-scan
Run an OpenTaint scan on project and produces the SARIF report. Use whenever the user asks to scan or re-scan a project
triage-dependencies
Mark which of a project's dependency libraries could introduce taint sources. Use to start source discovery
Security review for Claude-generated code. Pattern-based warnings on edits, LLM-powered diff review on Stop, and an agentic commit reviewer that catches injection, XSS, SSRF, hardcoded secrets, and 25+ other vulnerability classes.
Duende development skills and agents for Claude Code — covering OAuth/OIDC protocols, IdentityServer, token management, ASP.NET Core authentication/authorization, BFF patterns, and secure identity architecture
SAST analysis, dependency vulnerability scanning, OWASP Top 10 compliance, container security scanning, and automated security hardening
5 skills · 3 commands · 2 agents
wshobson/agents 42,461
Maintain appsec-workflow?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.