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 agentmods add skills/seenode/seenode-agent-plugin/domainsnpx skills add seenode/seenode-agent-plugin --skill domainsgit clone --depth 1 https://github.com/seenode/seenode-agent-pluginWhat 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 | $0.00060 | $0.00559 |
| Opus 5 | $0.00030 | $0.00280 |
| Sonnet 5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
domains 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 yesterday.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom domains on Seenode
Only web applications support custom domains. Workers and private apps do not.
Web apps already receive a default *.seenode.app domain on creation — use this skill for custom domains.
List current domains
list_domains(application_id=...)
Unverified domains include dnsSetup with the exact CNAME/A records to create. Never describe an unverified domain as working.
Add a domain
add_domain(
application_id=...,
domain_name="example.com",
default=false
)
Notes:
- For an apex like
example.com, Seenode also attacheswww.example.com(and vice versa). Expect multiple records — each needs DNS. default=truemakes this the application’s primary domain.- Side effects: creates domain records and queues background DNS verification. The domain is not live until DNS + TLS + routing succeed.
Report every returned DNS record to the user clearly (type, name, value).
Update default domain
update_domain(application_id=..., domain_id=..., default=true|false)
Use after list_domains to resolve domain_id. Confirm with the user before changing which custom domain is primary.
Verify / poll status
After the user creates DNS records:
check_domain_status(
application_id=...,
domain_name="example.com"|null,
domain_id=null
)
Per domain flags:
| Field | Meaning |
|---|---|
dnsReady |
DNS verified by Seenode |
sslReady |
Certificate READY |
routeReady |
Attached to the running app |
ready |
All three true |
When not ready, use pending and dnsSetup. There is no force re-check — wait between polls. Only claim success when ready is true.
Safety
- Do not claim the domain works until
ready. - No delete-domain tool via MCP — remove domains in the dashboard.
- Confirm the target app is
webviaget_applicationbefore adding.
Relevant tools
list_domains, add_domain, update_domain, check_domain_status, get_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.
- yesterday First seen · 83 lines · 60 tokens per session scan A eef3b56112d5
domains is a skill published in the GitHub repository seenode/seenode-agent-plugin (2 stars, last pushed 23d ago), licensed MIT. It adds 60 tokens to every session and 559 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…