Figma From Code Discovery Assets
bitovi/ai-enablement-prompts
Subagent for figma-from-code Phase 0b. An agent skill from bitovi/ai-enablement-prompts.
Run one stage of the OpenTaint pipeline by coordinating leaf subagents and deterministic joins.
$ npx skills add seqra/opentaint --skill orchestrate-stage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seqra/opentaint orchestrate-stage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/seqra/opentaint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/orchestrate-stage .claude/skills/orchestrate-stage && rm -rf skills-srcUse ~/.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/
Install the "orchestrate-stage" agent skill from https://github.com/seqra/opentaint/tree/main/skills/orchestrate-stage into .claude/skills/orchestrate-stage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-stage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/seqra/opentaint/tree/main/skills/orchestrate-stageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add seqra/opentaint --skill orchestrate-stage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seqra/opentaint orchestrate-stage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seqra/opentaint.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/orchestrate-stage .agents/skills/orchestrate-stage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orchestrate-stage" agent skill from https://github.com/seqra/opentaint/tree/main/skills/orchestrate-stage into .agents/skills/orchestrate-stage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-stage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seqra/opentaint --skill orchestrate-stage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seqra/opentaint orchestrate-stage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seqra/opentaint.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/orchestrate-stage .cursor/skills/orchestrate-stage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "orchestrate-stage" agent skill from https://github.com/seqra/opentaint/tree/main/skills/orchestrate-stage into .cursor/skills/orchestrate-stage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-stage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/seqra/opentaint.git --path skills/orchestrate-stage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add seqra/opentaint --skill orchestrate-stage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seqra/opentaint orchestrate-stage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seqra/opentaint.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/orchestrate-stage .gemini/skills/orchestrate-stage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "orchestrate-stage" agent skill from https://github.com/seqra/opentaint/tree/main/skills/orchestrate-stage into .gemini/skills/orchestrate-stage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-stage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install seqra/opentaint orchestrate-stageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add seqra/opentaint --skill orchestrate-stage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seqra/opentaint.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/orchestrate-stage .github/skills/orchestrate-stage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "orchestrate-stage" agent skill from https://github.com/seqra/opentaint/tree/main/skills/orchestrate-stage into .github/skills/orchestrate-stage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-stage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seqra/opentaint --skill orchestrate-stage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install seqra/opentaint orchestrate-stage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seqra/opentaint.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/orchestrate-stage .opencode/skills/orchestrate-stage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "orchestrate-stage" agent skill from https://github.com/seqra/opentaint/tree/main/skills/orchestrate-stage into .opencode/skills/orchestrate-stage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-stage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
orchestrate-stageRun one stage of the OpenTaint pipeline by coordinating leaf subagents and deterministic joins.
Orchestrate Stage is an agent skill from seqra/opentaint. 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
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `references/approx-round.md`, `references/escalation.md` and `references/poc.md`).
It sits in Security, covering Subagents and 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.
Read from SKILL.md and the folder at commit f945f92. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
uvpython3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Orchestrate Stage loads about 806 tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 45 tokens; SKILL.md has 359 words of instructions outside code blocks.
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.
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); the scripts in this folder are not scanned.
The full file from seqra/opentaint at commit f945f92, republished under its Apache-2.0 licence (© seqra). 359 words, ~806 tokens.
.claude/skills/orchestrate-stage/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.Complete one bounded stage of the OpenTaint security workflow. Dispatch its independent work to leaf subagents within the resource caps and run the deterministic plan/join scripts its reference names. All durable state lives under the project's .opentaint/ tree.
Match the stage keyword to its reference and read it fully:
sources → <skill-dir>/references/sources.md
approx-round → <skill-dir>/references/approx-round.md
sinks → <skill-dir>/references/sinks.md
triage → <skill-dir>/references/triage.md
poc → <skill-dir>/references/poc.md
escalation → <skill-dir>/references/escalation.mdRun the bundled script to get the setup overview before proceeding to the reference's instructions:
uv run <skill-dir>/scripts/get_status.py --fullUse uv run <skill-dir>/scripts/get_status.py at a stage gate or join, or when an updated list of remaining work is needed. It is the read-only view of the current stage.
Finish with one concise summary: counts completed and terminal items with one-line causes. Never paste file contents.
Launch leaf subagents from the project root. They inherit that working directory, so omit project-root. One dispatch loads exactly one leaf skill and performs only that skill's task. Follow this template when dispatching subagent:
Invoke the Skill <skill-name> first, then follow its instructions precisely
Inputs:
<id-or-flag>: <value>Pass language from get_status.py --full to every language-coupled leaf.
Universal rules:
<skill-dir>/references/escalation.md, settle that item, and continue. Only a blocker shared by every remaining item stops the stageFan-out and caps:
get_status.py --full prints global and heavy caps; the heavy leaves in these stages are create-rule and create-dataflow-approximation. Never exceed either cap; reduce global by 1 for the rest of the stage when a leaf is rate-limitedget_status.py, not by hand — don't re-derive it with glob/grep/python3 -c/YAML scans over .opentaint/tracking, results, or the *.yaml. If its output doesn't settle the question, re-run get_status.py --full before opening any file; hand-scanning the tree balloons the run's context© 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
SKILL.md and 9 other files (scripts, references) in skills/orchestrate-stage of seqra/opentaint.
Open the folder on GitHubat commit f945f92
Orchestrate Stage 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Orchestrate Stage this skillseqra/opentaint | 162 | — | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Figma From Code Discovery Assetsbitovi/ai-enablement-prompts | 121 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Security AuditorArchethect/sc-auditor | 127 | — | ~5.9k | Automated safety check: Notes | None | |
| Trailofbits Harnessautonomous-ai/openharness | 1.1k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Agent Bom RegistryLeoYeAI/openclaw-master-skills | 2.2k | — | ~969 | Automated safety check: Pass | Apache-2.0 | |
| Semgrepvigolium/piolium | 138 | 1 repos | ~2.4k | Automated safety check: Notes | MIT |
bitovi/ai-enablement-prompts
Subagent for figma-from-code Phase 0b. An agent skill from bitovi/ai-enablement-prompts.
Archethect/sc-auditor
Interactive smart contract security audit using Map-Hunt-Attack methodology with static analysis, parallel hunt lanes, skeptic-judge verification, and structured reporting.
autonomous-ai/openharness
Use in every Trail of Bits Skills workspace inside Harness, before any audit skill — the findings.json format the report pane is built from, which Trail of Bits skill serves which audit phase, and…
LeoYeAI/openclaw-master-skills
MCP server security registry and trust assessment — look up servers in the 427+ server security metadata registry, run pre-install marketplace checks, batch fleet risk scoring, assess skill file…
vigolium/piolium
Run Semgrep static analysis scan on a codebase using parallel subagents.
Narwhal-Lab/MagicSkills
Parse C source code into an Abstract Syntax Tree (AST). An agent skill from Narwhal-Lab/MagicSkills.
seqra/opentaint
Analyze an OpenTaint scan's dropped external methods and decide which of them are propagators and optionally sinks.
seqra/opentaint
Model a method's taint propagation as code-based dataflow approximation and refine it against a test project until the sample passes.
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.
seqra/opentaint
Build a target project into an opentaint project model. An agent skill from seqra/opentaint.
seqra/opentaint
Model a method's taint propagation as a passThrough approximation.
seqra/opentaint
Author and verify an OpenTaint rule. An agent skill from seqra/opentaint.
Categories
Run one stage of the OpenTaint pipeline by coordinating leaf subagents and deterministic joins. Orchestrate Stage is an agent skill from seqra/opentaint. Run one stage of the OpenTaint pipeline by coordinating leaf subagents and deterministic joins.
Orchestrate Stage fits situations like: A separate OpenTaint pipeline stage needs to be executed; tasks that involve Subagents; tasks that involve Static analysis and SAST.
Run `npx skills add seqra/opentaint --skill orchestrate-stage -a claude-code`. Or copy the skill folder (skills/orchestrate-stage in seqra/opentaint) into .claude/skills/orchestrate-stage in your project. Claude Code loads it when a task matches its description.
Run `npx skills add seqra/opentaint --skill orchestrate-stage -a codex`. Or copy the skill folder (skills/orchestrate-stage in seqra/opentaint) into .agents/skills/orchestrate-stage in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seqra/opentaint --skill orchestrate-stage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestrate-stage, .gemini/skills/orchestrate-stage, .github/skills/orchestrate-stage and .opencode/skills/orchestrate-stage in your project.
Going by SKILL.md and its folder, Orchestrate Stage needs Python for the scripts in its folder and the command-line tools its instructions call (uv and python3). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Orchestrate Stage 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.
About 806 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Orchestrate Stage: Figma From Code Discovery Assets (bitovi/ai-enablement-prompts, 121 stars), Security Auditor (Archethect/sc-auditor, 127 stars), Trailofbits Harness (autonomous-ai/openharness, 1.1k stars) and Agent Bom Registry (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.