genefoundry-router: Skill for Claude Code

.claude/skills/fleet-standard-adoption/SKILL.md

fleet-standard-adoption is a skill for Claude Code from berntpopp/genefoundry-router. It costs 46 tokens per session (504 once invoked), scanned A, original, MIT.

A set of instructions for bringing a code repository into line with defined engineering standards, such as naming, error responses, versioning, container security, communication protocols, and logging. A repository is the project folder containing its code and configuration.

In plain words
What is it for?
Use it when adopting GeneFoundry fleet standards, updating tools or error responses, hardening containers, fixing version metadata, checking MCP communication, improving logging, or closing the related tracking issue.
Why use it?
It helps find and close gaps between the repository and the required standards. This reduces inconsistent interfaces, unsafe container settings, unclear versions, and unsuitable logs.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is berntpopp/genefoundry-router's own configuration. It tells Claude Code how to work on genefoundry-router itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything genefoundry-router configures →

Reuse

Borrowing it

Nothing to install: this file belongs to berntpopp/genefoundry-router. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/berntpopp/genefoundry-router/main/.claude/skills/fleet-standard-adoption/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/berntpopp/genefoundry-router

Made for: Claude Code.

Wrote 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.

agentmods badge for fleet-standard-adoption

README.md
[![agentmods](https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/fleet-standard-adoption/github.svg)](https://agentmods.dev/skills/berntpopp/genefoundry-router/fleet-standard-adoption)
Your own site
<a href="https://agentmods.dev/skills/berntpopp/genefoundry-router/fleet-standard-adoption"><img src="https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/fleet-standard-adoption/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.

agentmods 80×15 button for fleet-standard-adoption

Your own site · 80×15
<a href="https://agentmods.dev/skills/berntpopp/genefoundry-router/fleet-standard-adoption"><img src="https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/fleet-standard-adoption.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 504 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00504
Opus 5 $0.00023 $0.00252
Sonnet 5 $0.00009 $0.00101
Haiku 4.5 $0.00005 $0.00050

Measured 11d ago against content hash a29ccbc3716a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

fleet-standard-adoption 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 11d 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.

Origin

Copies of this mod

6 near-identical copies found in the catalogue:

.claude/skills/fleet-standard-adoption/SKILL.md · 29 lines

What it actually says

Fleet-Standard Adoption

Follow AGENTS.md first. The canonical standards live under docs/ (the sibling router repo for *-link; docs/ in the router):

  • TOOL-NAMING-STANDARD-v1.mdverb_noun snake_case, stable, collision-free names (lets the router drop any transform).
  • RESPONSE-ENVELOPE-STANDARD-v1.1.md (current; supersedes v1) — success, the payload, flat execution-error fields (error_code / message / retryable / recovery_action), and _meta (data_version). v1.1 adds untrusted-content fencing and error-message sanitation (fixed/enum error fields — never reflect caller-supplied or upstream text into caller-visible fields or logs; see the FastMCP not-found reflection guard). The nested error:{...} shape is deferred — don't use it.
  • CONTAINER-HARDENING-STANDARD-v1.md — non-root, read-only, cap-drop, digest-pin, Trivy + SBOM.
  • VERSIONING-STANDARD-v1.md — single-source metadata version; no serverInfo.version framework leak.
  • MCP-TRANSPORT-STANDARD-v1.md — single stateless /mcp (no 307 split), canonical serverInfo / health.
  • Logging & CLI Standard v1 — structured logging + CLI conventions (canonical text tracked per-repo; no router doc).

Workflow

  1. Read the standard's Definition of Done; check this repo against it.
  2. Apply the smallest change that meets the DoD; reuse the router's reference implementation rather than reinventing.
  3. Add or update the guard test the standard specifies so the change can't regress.
  4. Run make ci-local; note residual risk.
  5. Close the standard's tracking issue with a one-line CHANGELOG note.

Common mistakes

  • Adding router-side workarounds instead of fixing the backend to the standard.
  • Meeting the letter without the guard test — it regresses on the next change.
Changes

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.

  1. 11d ago First seen · 29 lines · 46 tokens per session scan A a29ccbc3716a

Subscribe to this mod's changes

fleet-standard-adoption is a skill published in the GitHub repository berntpopp/genefoundry-router (5 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 504 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.

Related

Other skills, from other repositories

code-review

Use before opening a pull request, marking one ready for review, or pushing further commits to a branch with an open pull request — or when asked to review a diff or a PR. Reviews the cumulative diff against the project's written commitments and reports evidence-grounded findings; works with any coding agent and needs…

pvliesdonk/markdown-vault-mcp · 68 tokens

pr-alignment-loop

Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to…

nikships/skills-registry · 122 tokens

pep8-code-style-compliance-verification

Use when developing or reviewing Python code for a scientific package (e.g., cooltools) that targets collaborative development with multiple contributors.

HolobiomicsLab/asb-skill-collections · 35 tokens

reviewing-update-sets

Reviewing, analyzing, and comparing ServiceNow update sets before promotion. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, "what changed in this update set," or…

jschuller/mcp-server-servicenow · 77 tokens

code-standards

Checks code against organizational standards for naming conventions, documentation, error handling, and code quality.

aws-samples/serverless-samples · 0 tokens

security-review

Performs a security review of code changes, checking for common vulnerabilities and security issues.

aws-samples/serverless-samples · 0 tokens