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 reopt-ai/reopt-skills --skill data-sdk-integrationgit clone --depth 1 https://github.com/reopt-ai/reopt-skillsWrote 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/reopt-ai/reopt-skills/data-sdk-integration)<a href="https://agentmods.dev/skills/reopt-ai/reopt-skills/data-sdk-integration"><img src="https://agentmods.dev/badge/skills/reopt-ai/reopt-skills/data-sdk-integration/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/reopt-ai/reopt-skills/data-sdk-integration"><img src="https://agentmods.dev/badge/skills/reopt-ai/reopt-skills/data-sdk-integration.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00102 | $0.01273 |
| Opus 5 | $0.00051 | $0.00636 |
| Sonnet 5 | $0.00020 | $0.00255 |
| Haiku 4.5 | $0.00010 | $0.00127 |
Grade A, and why
data-sdk-integration 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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
reopt Data SDK Integration
Load data-sdk-install first; this skill owns product instrumentation after transport setup.
1. Establish the real baseline
- Inspect the framework, package manager, routes, auth/session model, existing analytics providers, event helpers, consent owner, server-confirmed outcomes, and tests. Preserve useful existing contracts instead of creating a parallel taxonomy.
- Read installed client/server READMEs before choosing APIs. The catalogue
commands come from
@reopt-ai/data-cli(binreopt-data, Node 22+, dev dependency); read its README and the livereopt-data event --helpbefore using them. Never import the deprecated@reopt-ai/data-sdkmeta-package. - Identify the Data project and credentials. Do not invent IDs, commit live placeholders, or provision remote resources without user authorization.
2. Write the measurement plan before call sites
- Start from decisions: acquisition, activation, engagement, completion, retention, sharing, and qualified conversion. Define a short funnel for each journey and state what question every event answers.
- Use stable snake_case names and properties. Prefer durable IDs, enums, booleans, counts, durations, and bounded categories; reject free text, full URLs with sensitive query parameters, direct PII, and high-cardinality rollup keys.
- Record attempts and outcomes separately. Emit authoritative outcomes only after the server or durable store confirms them.
- Give page views, web vitals, and lifecycle events one owner to prevent duplicates.
3. Make the contract executable
- Create or extend one typed event registry containing description, required properties, conversion intent, and useful dimensions. Validate before delivery in development and cover required-property rules with tests.
- Build one privacy sanitizer and event-envelope builder. Fan the same payload to existing providers and remove provider-only fields at adapter boundaries.
- Once the real project ID is known, initialize
reopt-data.events.jsonwithreopt-data event init(orevent pullfrom an existing server catalogue). Mark only true business outcomes as conversions and select at most the low-cardinality properties needed for recurring rollups. Commit the catalogue andreopt-data.events.lock.json; runevent diff, thenevent push(plan) beforeevent push --apply --yes; gate CI withevent verify. - Generate
reopt-data event types --out src/reopt-events.d.tsand type the sharedtrack()wrapper withReoptEventName/ReoptEventPropertiesso undeclared events fail at compile time.
What ships with it
2 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.
- 5d ago First seen · 106 lines · 102 tokens per session scan A df5e332492f8
data-sdk-integration is a skill published in the GitHub repository reopt-ai/reopt-skills (1 stars, last pushed 6d ago), licensed MIT. It adds 102 tokens to every session and 1,273 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…