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 nip46-nostrconnect-url-paramsgit 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/nip46-nostrconnect-url-params)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/nip46-nostrconnect-url-params"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/nip46-nostrconnect-url-params/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/nip46-nostrconnect-url-params"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/nip46-nostrconnect-url-params.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.00109 | $0.00847 |
| Opus 5.5 | $0.00044 | $0.00339 |
| Sonnet 5.5 | $0.00022 | $0.00169 |
| Haiku 4.5 | $0.00011 | $0.00085 |
Grade A, and why
nip46-nostrconnect-url-params 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NIP-46 nostrconnect:// URL Parameter Format
Problem
When implementing NIP-46 client-initiated connections (nostrconnect://), signer apps may fail to recognize the URL if app metadata is passed as a JSON object instead of separate query parameters.
Context / Trigger Conditions
- Signer app (Amber, nsec.app, nsecBunker) shows error or fails silently when scanning/pasting URL
- URL contains
metadata={"name":"...","url":"..."}format - QR code generates successfully but signer doesn't connect
- Other parameters (relay, secret, perms) appear correct
Solution
Wrong (metadata JSON object):
nostrconnect://<pubkey>?relay=wss://relay.example.com&secret=abc123&metadata={"name":"MyApp","url":"https://myapp.com","icon":"https://myapp.com/icon.png"}&perms=sign_event
Correct (separate parameters per NIP-46):
nostrconnect://<pubkey>?relay=wss://relay.example.com&secret=abc123&name=MyApp&url=https://myapp.com&image=https://myapp.com/icon.png&perms=sign_event
Code fix example (Dart):
// WRONG - Don't bundle in metadata JSON
if (metadata.isNotEmpty) {
final metadataJson = jsonEncode(metadata);
params.add('metadata=${Uri.encodeComponent(metadataJson)}');
}
// CORRECT - Use separate params as specified in NIP-46
if (appName != null && appName.isNotEmpty) {
params.add('name=${Uri.encodeComponent(appName)}');
}
if (appUrl != null && appUrl.isNotEmpty) {
params.add('url=${Uri.encodeComponent(appUrl)}');
}
if (appIcon != null && appIcon.isNotEmpty) {
params.add('image=${Uri.encodeComponent(appIcon)}');
}
Verification
- Generate a nostrconnect:// URL
- Verify URL contains
name=,url=,image=as separate params (notmetadata=) - Test with signer app (Amber Android, nsec.app web, or nsecBunker)
- Signer should show app name and prompt for approval
NIP-46 Spec Reference
From NIP-46:
Additional information should be passed as query parameters:
name(optional) - the name of the client applicationurl(optional) - the canonical url of the client applicationimage(optional) - a small image representing the client application
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.
- 1mo ago First seen · 84 lines · 109 tokens per session scan A daf4ef4a7b52
nip46-nostrconnect-url-params is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 109 tokens to every session and 847 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-09-03.
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.
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.
consensus-math-correctness
L1 trigger - audits consensus arithmetic for truncation, unused bounds, EMA direction, and threshold edge errors.
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…
finish-it
Get a stalled or sprawling game project to ship: diagnose the death loop, cut to the core, set a binary finish line.