New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Report Analyzer Issue

by seqra in seqra/opentaint

Write a self-contained OpenTaint engine-issue report from an analysis diagnosis or a full-scan failure.

Apache-2.0Auto-check passedSecurity

Install Report Analyzer Issue

skills CLI
$ npx skills add seqra/opentaint --skill report-analyzer-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install seqra/opentaint report-analyzer-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/seqra/opentaint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/report-analyzer-issue .claude/skills/report-analyzer-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
report-analyzer-issue
GitHub stars
162
Token cost
~1.1k tokens
SKILL.md length
616 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Write a self-contained OpenTaint engine-issue report from an analysis diagnosis or a full-scan failure.

  • Works in 2 steps: Gate → Write the report
  • An engine-side issue needs a report
  • SKILL.md covers Inputs, Workflow and Output
  • Calls git

What it does

Report Analyzer Issue is an agent skill from seqra/opentaint. 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

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Static analysis and SAST. The repository describes itself as: The open source taint analysis engine for the AI era. A formal dataflow analysis tool you can customize and self-host, built so AI agents drive your application security analysis… The licence is Apache-2.0.

When your agent uses it

  • An engine-side issue needs a report
  • Tasks that involve Static analysis and SAST

Example prompts

  • “/report-analyzer-issue”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Gate
  2. Write the report

What it can do on your machine

Read from SKILL.md and the folder at commit f945f92. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Report Analyzer Issue loads about 1.1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 616 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from seqra/opentaint at commit f945f92, republished under its Apache-2.0 licence (© seqra). 616 words, ~1,143 tokens.

Download SKILL.mdSave it as .claude/skills/report-analyzer-issue/SKILL.md (or your agent's skills folder).
name
report-analyzer-issue
description
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
license
Apache-2.0
metadata.author
opentaint
metadata.version
0.3.0

Skill: Report Analyzer Issue

Turn a suspected engine-level problem into a self-contained .opentaint/issues/<slug>.md report. It runs no analysis of its own — it only writes the report from what the caller supplies. Two kinds:

  • an analysis issue — a suspected engine-level taint-propagation problem the caller couldn't resolve with a rule or a model (the analyzer's result looks wrong)
  • a resource issue — a full-project scan that produced no SARIF after its allowed retry, memory bound, or timeout backstop; no taint diagnosis, just the setup that triggered it so the engine team can reproduce

Inputs

Provided by the caller, fall back to the default value when omitted. Ask back only when a required input is missing and has no sensible default

  • project-root (optional) — root of the target project. Opentaint keeps all analysis artifacts under the fixed <project-root>/.opentaint/ directory, so every .opentaint/... path below resolves there. Default: current directory
  • diagnosis (required for analysis) — the caller's brief engine-level cause: roughly where taint appears to die and why. A short hand-off, not a proven trace
  • artifact (required for analysis) — the rule or approximation the issue concerns: a rule's full id and ruleset, or the approximation's target method(s)
  • name (optional, analysis) — the test-project name the artifact was traced on; its tree is .opentaint/test-projects/<name> and model .opentaint/test-compiled/<name>, cited so the engine team can reproduce
  • setup (required for resource) — what was running when the scan failed without SARIF: the ruleset(s), approximation dirs, project model, final memory bound, timeout/backstop outcome, scan log, and commit hash (git rev-parse HEAD)

Workflow

1. Gate

The inputs pick the kind: a diagnosis (+ artifact) is an analysis issue, a setup is a resource issue.

For an analysis issue, write from the caller's brief cause as supplied — don't verify, reproduce, or run anything yourself. This is a first-pass approximate hand-off to the engine team, not a proven diagnosis; whatever the caller gives is enough to write the report.

For a resource issue, the gate is simpler: the caller confirms the full-project scan completed its allowed retry/backstop without producing valid SARIF. No taint diagnosis is required — write the report from the setup.

Show full SKILL.md (272 more words)Show less
2. Write the report

Write .opentaint/issues/<slug>.md — the self-contained deliverable, <slug> a short kebab-case symptom name. Open with a fixed header so the engine team can triage at a glance, then free-form detail below it.

Header (both kinds):

  • Type — analysis or resource
  • Setup — the exact command that reproduces it: the opentaint test rule … / test approximation run for analysis, or the failed opentaint scan for resource, each with its model, rulesets, and approximation dirs (plus final memory and timeout/backstop outcome for resource)
  • Run logs — the run's log files, by path: for analysis, any debug log or fact-reachability SARIF the caller cited, if present; for resource, the scan's output log
  • Minimal repro — the smallest set of files/folders that demonstrates it: for analysis, the test project .opentaint/test-projects/<name> if one was named; for resource, the project model, rulesets, and approximation dirs in play (with their rough size)
  • TL;DR — 2–3 sentences: the symptom, and for analysis where taint appears to die and what the engine should do instead

Below the header, free-form — whatever makes the case, at least:

  • analysis — the artifact under test (rule id + ruleset, or approximation target method(s)); the caller's brief cause; observed vs expected and any fact-reachability trace, if the caller supplied them; a 1–3 sentence hypothesis of what the engine does wrong (a hypothesis, not a fix)
  • resource — the model's rough size (classes/modules if known) and the commit hash (git rev-parse HEAD) it was built from

Keep it tight: the header plus about one screen of body.

Output

Artifacts
  • .opentaint/issues/<slug>.md — the self-contained issue report (the deliverable)
Summary
  • the kind (analysis / resource) and the one-line symptom; for an analysis issue, where taint appears to die

© seqra, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/report-analyzer-issue of seqra/opentaint.

Open the folder on GitHubat commit f945f92

Compare with similar skills

Report Analyzer Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Report Analyzer Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Report Analyzer Issue this skillseqra/opentaint162—~1.1kAutomated safety check: PassApache-2.0
Semgrepvigolium/piolium1381 repos~2.4kAutomated safety check: NotesMIT
C To AstNarwhal-Lab/MagicSkills316—~1.1kAutomated safety check: PassMIT
Semgrep Security Scantrailofbits/skills7.4k—~3.7kAutomated safety check: NotesCC-BY-SA-4.0
LLM Sast ScannerSunWeb3Sec/llm-sast-scanner286—~6.2kAutomated safety check: PassNone
Sast SemgrepAgentSecOps/SecOpsAgentKit2192 repos~2.4kAutomated safety check: PassCustom licence

Similar skills

  • Semgrep

    vigolium/piolium

    Run Semgrep static analysis scan on a codebase using parallel subagents.

    138 GitHub starsUsed in 1 repo~2.4k tokens
    SecurityAuto-check: notes

  • C To Ast

    Narwhal-Lab/MagicSkills

    Parse C source code into an Abstract Syntax Tree (AST). An agent skill from Narwhal-Lab/MagicSkills.

    316 GitHub stars~1.1k tokensUpdated 6 mo ago
    SecurityAuto-check passed

  • Semgrep Security Scan

    trailofbits/skills

    Official

    Detects languages, proposes rulesets for approval, then runs the approved Semgrep scan across a codebase and merges the output into one SARIF file.

    7.4k GitHub stars~3.7k tokensUpdated 5 days ago
    SecurityAuto-check: notes

  • LLM Sast Scanner

    SunWeb3Sec/llm-sast-scanner

    General-purpose Static Application Security Testing (SAST) skill for code vulnerability analysis.

    286 GitHub stars~6.2k tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Sast Semgrep

    AgentSecOps/SecOpsAgentKit

    Static application security testing (SAST) using Semgrep for vulnerability detection, security code review, and secure coding guidance with OWASP and CWE framework mapping.

    219 GitHub starsUsed in 2 repos~2.4k tokens
    SecurityAuto-check passed

  • Wp Phpstan

    Automattic/agent-skills

    A skill your agent uses when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and…

    211 GitHub starsUsed in 1 repo~1k tokens
    SecurityAuto-check passed

More from seqra/opentaint

All 16 skills in this repo

  • Analyze External Methods

    seqra/opentaint

    Analyze an OpenTaint scan's dropped external methods and decide which of them are propagators and optionally sinks.

    162 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Create Dataflow Approximation

    seqra/opentaint

    Model a method's taint propagation as code-based dataflow approximation and refine it against a test project until the sample passes.

    162 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Orchestrate Stage

    seqra/opentaint

    Run one stage of the OpenTaint pipeline by coordinating leaf subagents and deterministic joins.

    162 GitHub stars~806 tokensUpdated today
    Auto-check passed

  • Appsec Agent

    seqra/opentaint

    Run an end-to-end OpenTaint application-security analysis while owning the long project build and scans and delegating each other pipeline stage.

    162 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Build Project

    seqra/opentaint

    Build a target project into an opentaint project model. An agent skill from seqra/opentaint.

    162 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Create Pass Through Approximation

    seqra/opentaint

    Model a method's taint propagation as a passThrough approximation.

    162 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Report Analyzer Issue

What does Report Analyzer Issue do?

Write a self-contained OpenTaint engine-issue report from an analysis diagnosis or a full-scan failure. Report Analyzer Issue is an agent skill from seqra/opentaint. Write a self-contained OpenTaint engine-issue report from an analysis diagnosis or a full-scan failure.

When should I use Report Analyzer Issue?

Report Analyzer Issue fits situations like: an engine-side issue needs a report; tasks that involve Static analysis and SAST.

How do I install Report Analyzer Issue in Claude Code?

Run `npx skills add seqra/opentaint --skill report-analyzer-issue -a claude-code`. Or copy the skill folder (skills/report-analyzer-issue in seqra/opentaint) into .claude/skills/report-analyzer-issue in your project. Claude Code loads it when a task matches its description.

How do I install Report Analyzer Issue in Codex?

Run `npx skills add seqra/opentaint --skill report-analyzer-issue -a codex`. Or copy the skill folder (skills/report-analyzer-issue in seqra/opentaint) into .agents/skills/report-analyzer-issue in your project. Codex loads it when a task matches its description.

Can I use Report Analyzer Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seqra/opentaint --skill report-analyzer-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/report-analyzer-issue, .gemini/skills/report-analyzer-issue, .github/skills/report-analyzer-issue and .opencode/skills/report-analyzer-issue in your project.

What does Report Analyzer Issue need to run?

Going by SKILL.md and its folder, Report Analyzer Issue needs the command-line tools its instructions call (git).

Does Report Analyzer Issue access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Report Analyzer Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Report Analyzer Issue use?

Report Analyzer Issue is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Report Analyzer Issue use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Report Analyzer Issue?

Skills that share tags, products or a category with Report Analyzer Issue: Semgrep (vigolium/piolium, 138 stars), C To Ast (Narwhal-Lab/MagicSkills, 316 stars), Semgrep Security Scan (trailofbits/skills, 7.4k stars) and LLM Sast Scanner (SunWeb3Sec/llm-sast-scanner, 286 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Report Analyzer Issue?

seqra (a GitHub organization) maintains it in seqra/opentaint, which has 162 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 7, 2026.

Source: seqra/opentaint on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.