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 opengeni-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/opengeni-sites)<a href="https://agentmods.dev/skills/cloudgeni-ai/opengeni/opengeni-sites"><img src="https://agentmods.dev/badge/skills/cloudgeni-ai/opengeni/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/opengeni-sites"><img src="https://agentmods.dev/badge/skills/cloudgeni-ai/opengeni/opengeni-sites.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.00060 | $0.03712 |
| Opus 5 | $0.00030 | $0.01856 |
| Sonnet 5 | $0.00012 | $0.00742 |
| Haiku 4.5 | $0.00006 | $0.00371 |
Grade A, and why
opengeni-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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenGeni Sites
An OpenGeni 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, wildcard domain, provider-specific API wrapper, or OpenGeni-only build CLI.
Start from the durable Site
- 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.
Use normal Bun + React
Use the repository's pinned Bun version and ordinary package scripts. A minimal workflow is:
bun install
bun ./index.html
bun test
bun build --compile --target=browser ./index.html --outdir=dist
Install OpenGeni packages from the npm registry using the exact versions in
this Skill's package-versions.json. With skill_read, request
{"skill":"opengeni-sites","paths":["package-versions.json"]} and use the
returned package/version pairs in bun add --exact package@version ....
Reading a Skill does not create local files: do not assume a /workspace/.agents
path exists. If this Skill is already checked out, read the file at its actual
location instead. Do not use latest, canary, or version ranges. First check
for the local-development exception below. Keep these exact dependencies
in saved source. Missing expected exports indicate a package mismatch, not a
reason to replace the standard conversation component with custom wiring.
The pins include @opengeni/ogtool. Run bun run ogtool ... from this
project for discovery and calls; a sandbox-global CLI can predate the deployment.
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 Changed · +30 lines 92b33ca797a9
- 2d ago Changed · +121 lines 2169fba312f7
- 5d ago First seen · 175 lines · 60 tokens per session scan A a5f9ff2b4629
opengeni-sites is a skill published in the GitHub repository Cloudgeni-ai/opengeni (127 stars, last pushed today), licensed Apache-2.0. It adds 60 tokens to every session and 3,712 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-09-05.
Other skills, from other repositories
pn-ui-component-libraries
Curated UI/UX and component library knowledge. Recommends libraries for stack and use case; when shadcn MCP is available, use its tools to browse/search/install. Use when building UI, during discovery, or prior-art for frontend projects.
pn-threejs-core
Guides Three.js scenes, cameras, lighting, asset loading, animation, physics, and performance. Use when working on Three.js; covers scene structure, R3F/Drei patterns, WebGPU migration (r171+), TSL shaders, and compute shaders.
pn-react-next-perf
Optimizes React/Next.js data loading and rendering; avoids waterfalls, unnecessary client JS, and missing loading/error boundaries. Use when building or reviewing React or Next.js apps.
react-modernization
Master React version upgrades, class to hooks migration, concurrent features adoption, and codemods for automated transformation.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
fp-ts-react
Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15.