Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add web-abin/OpenGeno/plugin install opengenoWrote 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/web-abin/opengeno/geno-sync)<a href="https://agentmods.dev/skills/web-abin/opengeno/geno-sync"><img src="https://agentmods.dev/badge/skills/web-abin/opengeno/geno-sync.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.1 | $0.00088 | $0.02136 |
| Opus 5 | $0.00044 | $0.01068 |
| Sonnet 5 | $0.00018 | $0.00427 |
| Haiku 4.5 | $0.00009 | $0.00214 |
Grade A, and why
geno-sync 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 6d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/geno-sync
Detect and (optionally) reconcile drift between L3 feature docs and the code they describe. This is the second of OpenGeno's two skills; run it on demand when you suspect the tree is out of sync with code.
Pre-flight
test -d feat-tree || { echo "no tree — run /geno-init first"; exit 1; }
If no tree exists, abort with the message above.
Detect the tree's language
Before printing anything to the user, determine which language the tree is written in. Check, in order:
.feat-tree.jsonfor alanguagefield (added by future versions)CLAUDE.mdfor the OpenGeno injection block — look for "文档语言：中文" or "Doc language: English" inside the<!-- BEGIN OpenGeno -->/<!-- END OpenGeno -->markers- The actual content of
feat-tree/index.md— if its prose is in Chinese, use Chinese; otherwise English
Use that language for all output of this skill — drift summary, clarifying questions, reconciliation prompts, any new doc prose written during reconciliation.
Workflow
Step 1 — Run the drift checker
The script lives next to this skill (or in the global install location):
${CLAUDE_PLUGIN_ROOT}/scripts/drift-check.sh~/.claude/skills/geno-init/scripts/drift-check.sh.agents/skills/geno-init/scripts/drift-check.sh
(Note: scripts live under geno-init/scripts/ because that skill is
where they were installed; geno-sync reads them as siblings.)
Run it:
bash <path-to>/drift-check.sh
It prints lines like:
DRIFT feat-tree/auth/login.md lib/features/auth/login_page.dart 4
STUB feat-tree/onboarding/welcome.md
BROKEN feat-tree/legacy/old.md lib/legacy/old_screen.dart
STALE_SHA feat-tree/profile/edit.md abc123...
Step 2 — Categorize
Bucket the results into:
- red (
DRIFTlines with > 1 commit, especially with non-trivial diff) - yellow (
DRIFTwith 1 commit, or commits that look like refactor/format/comment-only) - gray (
STUB— never synced; awaiting first fill) - broken (
BROKEN— referenced code file no longer exists) - stale (
STALE_SHA— recorded SHA is no longer in git history, e.g. after a force-push)
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.
- 6d ago First seen · 225 lines · 88 tokens per session scan A ff52287e4f14
geno-sync is a skill published in the GitHub repository web-abin/OpenGeno (5 stars, last pushed 3mo ago), licensed MIT. It adds 88 tokens to every session and 2,136 once invoked, about $0.0004 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
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
clean-code
Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with long methods, unclear names, duplication or deep nesting. For how responsibilities are split across classes and which way dependencies point, use solid-principles instead.
architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
concurrency-review
Review Java concurrency code for thread safety, race conditions, deadlocks, and modern patterns (Virtual Threads, CompletableFuture, @Async). Use when user asks "check thread safety", "concurrency review", "async code review", or when reviewing multi-threaded code.
java-code-review
Systematic code review for Java with null safety, exception handling, concurrency, and performance checks. Use when user says "review code", "check this PR", "code review", or before merging changes.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.