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/jpd44/mesh44-plugins/domainnpx skills add jpd44/mesh44-plugins --skill domaingit clone --depth 1 https://github.com/jpd44/mesh44-pluginsWhat 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.00031 | $0.00850 |
| Opus 5 | $0.00015 | $0.00425 |
| Sonnet 5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
domain 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 2d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-kit:domain — Route 53 domain + delegated hosted zone
Why two accounts touch this
Domain registration lives in the management account (mgt, ID from aws.mgt_account_id in ~/.config/mesh44/config.json) for consolidated billing. The hosted zone the CDK stack uses lives in the child account so the stack can route53.HostedZone.fromLookup it without cross-account roles. We bridge them with an NS delegation.
Steps
1. Check availability
AWS_PROFILE=mgt aws route53domains check-domain-availability --domain-name "$DOMAIN"
If AVAILABLE, fetch the annual cost:
AWS_PROFILE=mgt aws route53domains list-prices --tld "$(echo $DOMAIN | awk -F. '{print $NF}')"
Quote the price to the user and require explicit OK before registering.
2. Register
AWS_PROFILE=mgt aws route53domains register-domain \
--cli-input-json file://register-domain.json
register-domain.json should use the contact info on file for other domains in this AWS account (the user can pull it from aws route53domains get-domain-detail --domain-name <existing-domain>). If no other domains are registered, ask the user for contact info before submitting. Privacy protection: AdminPrivacy=true, RegistrantPrivacy=true, TechPrivacy=true. Auto-renew: AutoRenew=true.
Registration takes 15–60 minutes. Don't block — kick it off, record the OperationId, and let the user know they'll get an email.
3. Create the hosted zone in the child account
AWS_PROFILE=child-<app-name> aws route53 create-hosted-zone \
--name "$DOMAIN" \
--caller-reference "$(date +%s)"
Capture the four NS records from the response.
4. Delete the auto-created zone in mgt and replace its NS records with the child's
Registration auto-creates a hosted zone in mgt. Delete it, or (safer) keep it but update its NS record set to point at the child zone's nameservers so DNS resolution flows through the child zone.
# In mgt — replace NS values with the four from step 3
AWS_PROFILE=mgt aws route53 change-resource-record-sets \
--hosted-zone-id "$MGT_ZONE_ID" \
--change-batch file://ns-change.json
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.
- 2d ago First seen · 95 lines · 31 tokens per session scan A b1a19943de48
domain is a skill published in the GitHub repository jpd44/mesh44-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 850 once invoked, about $0.0002 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
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…