Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/seqra/opentaint/orchestrate-stagenpx skills add seqra/opentaint --skill orchestrate-stagegit clone --depth 1 https://github.com/seqra/opentaintWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/seqra/opentaint/orchestrate-stage)<a href="https://agentmods.dev/skills/seqra/opentaint/orchestrate-stage"><img src="https://agentmods.dev/badge/skills/seqra/opentaint/orchestrate-stage.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00036 | $0.00733 |
| Opus 5 | $0.00018 | $0.00367 |
| Sonnet 5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
orchestrate-stage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run one stage
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.
Workflow
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.md
Run the bundled script to get the setup overview before proceeding to the reference's instructions:
uv run <skill-dir>/scripts/get_status.py --full
Use 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.
Dispatching
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:
- trust the returned summary; open an artifact only when the summary does not resolve the result
- don't read a leaf skill's contents unless genuinely needed
- never bundle multiple steps into one dispatch
- when a rule or approximation does not converge after its leaf's retries, load
<skill-dir>/references/escalation.md, settle that item, and continue. Only a blocker shared by every remaining item stops the stage
Fan-out and caps:
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 66 lines · 36 tokens per session scan A cda614714a28
orchestrate-stage is a skill published in the GitHub repository seqra/opentaint (149 stars, last pushed 5d ago), licensed Apache-2.0. It adds 36 tokens to every session and 733 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
plugin-code-review-orchestrated
Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.
github-issue-manager
Classifies a user request as Bug, Compatibility, Feature, Question, or Task for the explyt/spring-plugin GitHub repo, lightly researches the relevant codebase, searches similar existing issues, and either reports an existing issue or creates a correctly titled and labeled one following the repository issue forms. Use…
review-async-lifecycle
Normative reviewer for EDT safety, coroutines, cancellation, read/write actions, disposal, listeners and async lifecycle in the explyt spring-plugin. Use during orchestrated code review when the diff touches threading, background tasks, read or write actions, listeners, MessageBus, Disposable ownership or progress…
review-core-correctness
Normative mandatory reviewer for correctness, contracts, architecture sanity, UX behavior, code quality and tests in the explyt spring-plugin codebase. Use during orchestrated code review of a PR, diff, commit or branch, or when asked to review correctness, logic, architecture or test coverage of plugin changes.
review-findings-validator
Normative per-artifact validator: reads exactly one reviewer artifact, re-verifies every claim against real source code, classifies findings as TP, FP, or Need more data, and writes exactly one validated artifact. Use during the validation wave of an orchestrated code review, when asked to validate reviewer findings…
review-persistence-security-resources
Normative reviewer for persistence, settings, secrets, logging hygiene, resources, caches, cross-platform behavior and long-lived state in the explyt/spring-plugin IntelliJ plugin. Use when reviewing changes that touch PersistentStateComponent, settings UI, credentials, caches, service fields, logging, file paths…