Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add katareayush/video-captions/plugin install seedgenWrote 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/katareayush/video-captions/seedgen)<a href="https://agentmods.dev/skills/katareayush/video-captions/seedgen"><img src="https://agentmods.dev/badge/skills/katareayush/video-captions/seedgen/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/katareayush/video-captions/seedgen"><img src="https://agentmods.dev/badge/skills/katareayush/video-captions/seedgen.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.00130 | $0.01009 |
| Opus 5 | $0.00065 | $0.00504 |
| Sonnet 5 | $0.00026 | $0.00202 |
| Haiku 4.5 | $0.00013 | $0.00101 |
Grade A, and why
seedgen 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seedgen
You are generating a test-data seed script for the current repository. Be surgical and concise — produce something that runs on the first try.
If the user supplied arguments (a locale, a count, a scope), treat them as the request/filters; otherwise use the defaults noted in step 3.
1. Analyze the repo (read, don't guess)
Detect the stack and locate every place data is defined. Check for, in order of what exists:
- SQL / migrations:
*.sql,migrations/,schema.sql, Flyway/Liquibase. - ORM schemas: Prisma (
schema.prisma), Django (models.py), SQLAlchemy, TypeORM/Sequelize/Mongoose, Rails (db/schema.rb), Laravel migrations, GORM/Ent structs, Ecto. - Python: dataclasses, Pydantic models,
models.py. - Web3: Solidity (
*.sol), Hardhat/Foundry configs, ABI JSON, deploy scripts — data = on-chain seeding (mint, deploy, fund accounts, populate mappings). - APIs / types: OpenAPI/GraphQL schemas, TypeScript interfaces, protobuf.
- Config:
.env.example,docker-compose.yml, package manifest (package.json,pyproject.toml,Cargo.toml,go.mod,Gemfile) to learn the runtime, DB, and how existing scripts run.
Extract: entities/tables, field types, enums, NOT NULL / required, unique constraints, foreign keys and insertion order, and default values.
2. Pick the right output
Write the seed script in the project's own language and idiom so it drops in cleanly:
- Use the project's existing DB client / ORM / connection config (reuse
.env, never hardcode secrets). - Prefer the project's existing faker/factory lib if present; otherwise use a lightweight, well-known one for that ecosystem (
@faker-js/faker,faker/Faker, etc.), and add it to the manifest. - Respect FK order, satisfy every constraint, cover enums with a spread of values, and produce referentially consistent data (child rows point at real parents).
- Make it idempotent (safe to re-run: truncate/upsert or guard) and parameterized by count.
- Web3: emit a script for the project's toolchain (Hardhat/Foundry/ethers/web3.py) that deploys/uses contracts and seeds on-chain state against a local node.
What ships with it
1 file 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 · 47 lines · 0 tokens per session scan A d232a9bc80a9
seedgen is a skill published in the GitHub repository katareayush/video-captions (8 stars, last pushed 1mo ago), licensed MIT. It adds 130 tokens to every session and 1,009 once invoked, about $0.0006 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-31.
Other skills, from other repositories
data-migration
Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover, reconciling counts and values rather than assuming, handling the records that will not map cleanly, and planning a rollback that is actually executable.…
data-modeling
Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer analytics reads through. Use this to design or restructure a warehouse, model a new source, decide on grain or table structure, build a semantic or metric layer, or…
completion-verification
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of…
specify-incremental
Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.
testing
Writing effective tests and running them successfully. Covers layer-specific mocking rules, test design principles, debugging failures, and flaky test management. Use when writing tests, reviewing test quality, or debugging test failures.
domain-modeling
Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules.