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 skills add vincentkoc/dotskills --skill opik-integrations-auditorgit clone --depth 1 https://github.com/vincentkoc/dotskillsWrote 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/vincentkoc/dotskills/opik-integrations-auditor)<a href="https://agentmods.dev/skills/vincentkoc/dotskills/opik-integrations-auditor"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/opik-integrations-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vincentkoc/dotskills/opik-integrations-auditor"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/opik-integrations-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00053 | $0.00709 |
| Opus 5 | $0.00026 | $0.00354 |
| Sonnet 5 | $0.00011 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
opik-integrations-auditor 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 9d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opik Integrations Auditor
Purpose
Audit, compare, and document Opik integrations across Python, TypeScript, and backend OTEL/API surfaces with a repeatable evidence-first workflow.
When to use
Use this skill when the task involves:
- reviewing existing Opik integrations for behavior, coverage, or documentation quality
- designing or implementing a new integration
- producing integration pattern docs across Python, TypeScript, and OTEL/API
- identifying gaps between code, tests, and docs
Required outputs
Produce these artifacts in the response (or files if asked):
- Integration inventory table
- Pattern classification per integration
- Cross-surface comparison matrix (Python / TypeScript / OTEL/API)
- Findings list (bugs/risks/gaps)
- Documentation patch plan
- Test plan (unit + integration + e2e)
Workflow
- Build inventory and classify pattern per integration.
- Extract behavior contract (capture, streaming, errors, flush, span hierarchy).
- Extract data contract (usage, metadata/tags, thread propagation).
- Validate backend compatibility (OTEL endpoint/protocol/mapping rules).
- Review tests for coverage and missing edge cases.
- Produce documentation updates with consistent template.
Load references as needed
- For matrix schema and scoring:
references/matrix-and-rubric.md - For pattern definitions:
references/patterns.md - For evidence collection paths and commands:
references/evidence-collection.md - For documentation update template:
references/doc-template.md - For testing checklist:
references/testing-checklist.md - For subagent prompt templates:
references/subagent-prompts.md
Inputs
- Integration scope (specific integration or full inventory)
- Target surfaces to compare (Python, TypeScript, OTEL/API)
- Relevant repo paths and branch/diff scope
- Output expectations (table depth, doc patch format, test depth)
Outputs
- Inventory and comparison matrix
- Findings and risk summary
- Documentation patch plan
- Test plan with missing coverage calls
What ships with it
8 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.
- 9d ago First seen · 82 lines · 53 tokens per session scan A 71c21239c41b
opik-integrations-auditor is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 709 once invoked, about $0.0003 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
taiyi-plan
A TaiyiForge planning step that turns a README, product requirements document, or technical plan into a list of separate project changes. Each change includes a suggested work profile, dependencies, and priority.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.