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 Cloudgeni-ai/opengeni --skill sitesgit clone --depth 1 https://github.com/Cloudgeni-ai/opengeniWrote 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/cloudgeni-ai/opengeni/sites)<a href="https://agentmods.dev/skills/cloudgeni-ai/opengeni/sites"><img src="https://agentmods.dev/badge/skills/cloudgeni-ai/opengeni/sites/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/cloudgeni-ai/opengeni/sites"><img src="https://agentmods.dev/badge/skills/cloudgeni-ai/opengeni/sites.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00097 | $0.09729 |
| Opus 5.5 | $0.00039 | $0.03892 |
| Sonnet 5.5 | $0.00019 | $0.01946 |
| Haiku 4.5 | $0.00010 | $0.00973 |
Grade A, and why
sites 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
download URL in `downloads.source.url` using curl or Bun, then restore the How it starts
The opening of the file, as written. The whole thing — 762 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sites
A Site is an ordinary Bun web application with retained editable source (when supplied) and one published runtime file. React is the default, not a requirement: a plain HTML-only Site is valid. Build and test in the sandbox, then upload the self-contained HTML and optional source.
Do not invent a Site framework, deployment service, App Host, custom domain setup, provider-specific API wrapper, or platform-only build CLI. Putting a Site on the web is built in (see "Publish to the web").
Sites have no server; AI comes from the host
A Site never needs its own server, API key, or hosting provider to reach
the workspace. Model access, agent conversations, and workspace tools all come from
the host bridge: createOpenGeniSiteClient from @opengeni/sdk/site. Use its
ai.run helper for inline results, or @opengeni/react/session-ui when the app
needs a conversation surface. The parent page owns the
credentials and workspace identity; Site code receives neither, so "keep
credentials server-side" is already satisfied by that bridge.
When the user asks for AI, chat, an assistant, "Ask the data", or a "backend" inside a Site, that bridge is the design. Do not propose Vercel, another server, a tunnel, or a Connected Machine for workspace AI access, do not spawn a child to build a separate backend, and do not post a Connect card for a hosting provider the user did not name. Saved data needs no server either: Site Data (below) gives every published Site persistent collections and files, and scheduled tasks feed them through agent tools. A separate server is only relevant for a genuinely external need: a third-party API that requires a secret the viewer's browser must not hold, relational queries or volumes Site Data cannot serve, or live server-side compute. If the request seems to need one of those, or you cannot tell where the user wants the AI to run, say which designs are possible and ask before building.
Start from the durable Site
- For an existing page the user wants to view and share, consider Sites before choosing a temporary tunnel or another server. Inspect whether it can be packaged as self-contained HTML, preserve its design and behavior, and retain editable source when available. A local preview alone is still appropriate when that is all the user requests. The Site link opens only for workspace members; to share it wider, publish it to the web. Workspace AI and tool access are never such a backend (see above). If the app genuinely requires server-side compute that Sites cannot host, explain that constraint and ask how the user wants to proceed instead of dropping functionality or choosing a host.
- For a new Site, create a normal project directory with
package.json,index.html, TypeScript/React source, styles, tests, and any ordinary build configuration the app needs. - For an edit, call
opengeni__artifacts_get_sourcefirst and restore the download URL indownloads.source.urlusing curl or Bun, then restore the source bundle ({entrypoint, files: [{path, content}]}). If source is null, downloaddownloads.html.urland edit that HTML instead. URLs expire; call the tool again to refresh them. The returned current version id is the optimistic-concurrency fence for the next publish. - Treat retained source as the editable truth and the compiled HTML as the runtime projection. Never edit only the generated HTML when source exists.
- Keep secrets, Opengeni access keys, OAuth tokens, workspace ids, API base URLs, and signed URLs out of the source and generated HTML.
What ships with it
1 file 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.
- yesterday First seen · 762 lines · 97 tokens per session scan A b46f658edf67
sites is a skill published in the GitHub repository Cloudgeni-ai/opengeni (205 stars, last pushed today), licensed Apache-2.0. It adds 97 tokens to every session and 9,729 once invoked, about $0.0004 per session on Opus 5.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-10-21.
Other skills, from other repositories
playwright
Use when the task requires capturing or automating a real browser from the terminal.
effect-v4
Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all pinned exactly to [email protected] — Context.Service and explicit layers, Schema.TaggedError and typed recovery, the effect/cli command surface, and the vendored effect source oracle. Use when writing…
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
ax-cpp-gen
Use when writing C++ code with axllm for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
ax-java-gen
Use when writing Java code with dev.axllm:ax for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
ax-go-flow
Use when writing Go code with github.com/ax-llm/ax/packages/go for flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components.