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/create-rulenpx skills add seqra/opentaint --skill create-rulegit clone --depth 1 https://github.com/seqra/opentaintWhat 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.00019 | $0.02303 |
| Opus 5 | $0.00010 | $0.01151 |
| Sonnet 5 | $0.00004 | $0.00461 |
| Haiku 4.5 | $0.00002 | $0.00230 |
Grade A, and why
create-rule 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Create Rule
A unit names the source or sink methods of one side to detect. Write a library rule for each — reusing a built-in wherever one fits, authoring a custom one only for what none covers — and verify them against the unit's test project until every sample passes. Each rule exposes its tainted value under a consistent marker so a later stage can wire the real cross-package security joins. During this phase you write only the library rules and the throwaway joins to test them.
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 directorylanguage(required) — target language for this project and language-specific instructionsside(required) —sourcesorsinks; the unit's side. It selects the unit file, the sample style, and the test sub-projectunit(required) — the<package-kebab>identifying the unit. Its spec and tracking are in.opentaint/tracking/rules/<side>/<unit>.yaml; its test project is.opentaint/test-projects/<unit>/<side>and its compiled model.opentaint/test-compiled/<unit>/<side>fix-target(optional) — a created rule<path>#<id>the main scan flagged, plus the false positive or false negative to correct. When set, narrow or broaden that one rule instead of authoring from the unit
Workflow
1. Check existing coverage
Browse the built-in library rules for a source or sink you can reference — a refs to a built-in is cheaper and more accurate than authoring a completely new rule. The following command prints the built-in rules root path; browse it (layout per the language reference) and grep by your package's FQN:
opentaint health --rules
In fix mode, don't author from the unit: go straight to that one flagged rule, adjust it by the false-positive/negative guidance per step 4, re-run this side's tests, and stop — leave the unit's other entries untouched. Otherwise, when the unit's rules already exist and pass (entries carry rule_id and stages.tests_passing: done), reuse them as the baseline and extend only for what the unit newly names. When the unit is partway (some stages done, some not), continue from the first unfinished stage on the artifacts already on disk rather than restarting, authoring from scratch only the genuinely new sources or sinks.
What ships with it
3 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.
- 2d ago First seen · 133 lines · 19 tokens per session scan A 38b220c3a1f6
create-rule is a skill published in the GitHub repository seqra/opentaint (149 stars, last pushed 3d ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,303 once invoked, about $0.0001 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…