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 divinevideo/divine-mobile --skill divine-relay-video-requirementsgit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/divine-relay-video-requirements)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/divine-relay-video-requirements"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/divine-relay-video-requirements/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/divinevideo/divine-mobile/divine-relay-video-requirements"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/divine-relay-video-requirements.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.00105 | $0.00974 |
| Opus 5.5 | $0.00042 | $0.00390 |
| Sonnet 5.5 | $0.00021 | $0.00195 |
| Haiku 4.5 | $0.00011 | $0.00097 |
Grade A, and why
divine-relay-video-requirements 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 2mo 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Divine Relay Video Requirements
Problem
Publishing Kind 34236 (short-form video) events to divine relays fails with "blocked: event rejected by relay policy" even though the events comply with NIP-71 spec.
Context / Trigger Conditions
- Error message:
blocked: event rejected by relay policy - Kind 0 (profile) events publish successfully to the same relay
- Kind 34236 events fail on divine relays (wss://relay.poc.dvines.org, wss://relay.dvines.org)
- Events that work on other relays fail on divine relays
Root Cause
The divine relay (funnelcake) has additional validation beyond NIP-71:
From divine-funnelcake/crates/relay/src/relay.rs:554-564:
// divine.video requires thumbnail for all videos (stricter than NIP-71)
// Accept: thumb tag, thumbnail tag, image tag, or imeta with image field
let has_thumb = event.get_tag("thumb").is_some()
|| event.get_tag("thumbnail").is_some()
|| event.get_tag("image").is_some()
|| has_imeta_with_image(&event);
if !has_thumb {
// Event rejected
}
Solution
Ensure video events include a thumbnail in one of these formats:
-
Inside imeta tag (preferred - NIP-92 compliant):
["imeta", "url https://...", "m video/mp4", "image https://thumbnail.jpg", ...] -
Standalone tag:
["thumb", "https://thumbnail.jpg"] ["thumbnail", "https://thumbnail.jpg"] ["image", "https://thumbnail.jpg"]
Getting Thumbnails from Blossom
Blossom (media.divine.video) auto-generates thumbnails for uploaded videos:
- Thumbnail URL:
https://media.divine.video/{video_sha256}.jpg - Generation is async - may take a few seconds after upload
- Check with HEAD request before assuming availability
Verification
- Ensure imeta tag contains
image https://...field - Test publication:
nak event -k 34236 ... wss://relay.poc.dvines.org - Verify with:
nak req -k 34236 -a {pubkey} --limit 1 wss://relay.poc.dvines.org
Example
// Build imeta with thumbnail
const imetaParts = [
`url ${videoUpload.url}`,
"m video/mp4",
`image ${videoUpload.url}.jpg`, // Blossom thumbnail URL
"dim 480x480",
`x ${videoUpload.sha256}`,
"duration 6"
];
tags.push(["imeta", ...imetaParts]);
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.
- 2mo ago First seen · 104 lines · 105 tokens per session scan A 81818eaacc94
divine-relay-video-requirements is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 105 tokens to every session and 974 once invoked, about $0.0004 per session on Opus 5.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
code-changes
Workflow for any task that ends in code changes: issue analysis or triage, pull request review comments, features, bug fixes, refactors. Invoke at the start of such a task, before reading or writing code.
alchemy-cli
Use the Alchemy CLI (@alchemy/cli) for live blockchain data, transaction lookups, NFT/token/portfolio queries, simulation, tracing/debugging, contract reads/writes, wallet-signed sends, swaps and cross-chain bridges, Solana RPC/DAS plus wallet sends, webhook management, and Alchemy app administration. Preferred…
etherscan-transaction-debugger
Analyze and explain one or two EVM transactions using live Etherscan data and human-verifiable Etherscan evidence links. Use when a user provides a transaction hash or asks what happened, why a transaction failed, which contracts or internal calls were involved, where assets moved, whether a proxy implementation…
cross-environment-semantic-drift
L1 trigger - audits L1/L2 boundary bugs, precompile context assumptions, integer width mismatches at environment boundaries, and EVM-on-non-EVM drift.
genvm-lint
Validate GenLayer intelligent contracts with the GenVM linter.
consensus-math-correctness
L1 trigger - audits consensus arithmetic for truncation, unused bounds, EMA direction, and threshold edge errors.