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/jonnyton/tinyassets/infra-opsnpx skills add Jonnyton/TinyAssets --skill infra-opsgit clone --depth 1 https://github.com/Jonnyton/TinyAssetsWrote 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/jonnyton/tinyassets/infra-ops)<a href="https://agentmods.dev/skills/jonnyton/tinyassets/infra-ops"><img src="https://agentmods.dev/badge/skills/jonnyton/tinyassets/infra-ops.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00688 |
| Opus 5 | $0.00028 | $0.00344 |
| Sonnet 5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
infra-ops scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] DNS changes verified via `nslookup`/`curl -I`, not the UI's success toast How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infra Ops (Cloudflare + GoDaddy)
Operate the project's domain and edge infrastructure for the public surfaces
(tinyassets.io). Two providers, one skill; each has a detailed reference with
hard-won selectors, IPs, and gotchas — read the relevant one before acting.
Shared browser-lock discipline
Both providers' dashboards run through the host's CDP Chrome
(scripts/lead_browser.py) and obey the shared browser lock and one-tab rule:
python scripts/user_sim_auth_hook.py # expect 'no-browser' or 'approved'
python scripts/browser_lock.py acquire lead <provider>-<intent>
python scripts/browser_lock.py status # owner=lead
# ... do the work ...
python scripts/browser_lock.py release lead # always, even on failure
Never --force the lock unless you've verified the prior PID is dead. First use
of a provider in the Chrome-for-Testing profile hits SSO — ask the host to log in
once; the profile persists the session.
Cloudflare
DNS/Worker/token operations. Prefer the API (scripts/emergency_dns_flip.py
for DNS + Worker-route CRUD; wrangler deploy for Worker code) over dashboard
automation — the dashboard is a one-time gate to mint the API token. The Custom
Token form uses react-select and is unreliable to automate (>5 tool calls without
a green run → hand to the host). Full token scopes, rotation cadence, Monaco/Radix
selectors, and dashboard gotchas: references/cloudflare.md.
GoDaddy
Domain portfolio, DNS (only when GoDaddy manages the nameservers), SSL, and
Websites+Marketing. No first-class API — navigate the admin UI via
lead_browser.py. Key facts: W+M origin IPs 76.223.105.230 + 13.248.243.5
(apex A records) with www CNAME to the .godaddysites.com slug; Cloudflare
proxy must be DNS-only (gray) for those records or W+M SSL breaks; ignore stale
*.godaddysites.com prototypes — the real site binds to the custom domain. Known
URLs, DNS quirks, tour-popup dismissal, and pitfalls:
references/godaddy.md.
What ships with it
2 files 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.
- 3d ago First seen · 61 lines · 57 tokens per session scan A dc1cfc7e6190
infra-ops is a skill published in the GitHub repository Jonnyton/TinyAssets (1 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 688 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
terraform-skill
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code…
ondb
A logical analysis and reasoning tool for AI. Use when decomposing documents into structured knowledge, querying entities and relations, validating consistency, or indexing files. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", "analyze this document", entity CRUD, or cross-skill…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
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.