Borrowing it
Nothing to install: this file belongs to berntpopp/gencc-link. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/berntpopp/gencc-link/main/.claude/skills/fleet-standard-adoption/SKILL.mdgit clone --depth 1 https://github.com/berntpopp/gencc-linkWrote 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/berntpopp/gencc-link/fleet-standard-adoption)<a href="https://agentmods.dev/skills/berntpopp/gencc-link/fleet-standard-adoption"><img src="https://agentmods.dev/badge/skills/berntpopp/gencc-link/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.
<a href="https://agentmods.dev/skills/berntpopp/gencc-link/fleet-standard-adoption"><img src="https://agentmods.dev/badge/skills/berntpopp/gencc-link/fleet-standard-adoption.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.00046 | $0.00510 |
| Opus 5 | $0.00023 | $0.00255 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
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 9d 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.
This is a copy
97% identical to fleet-standard-adoption — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Fleet-Standard Adoption
Follow AGENTS.md first. The canonical standards live under ../genefoundry-router/docs/ (the sibling router repo for *-link; docs/ in the router):
TOOL-NAMING-STANDARD-v1.md—verb_nounsnake_case, stable, collision-free names (lets the router drop anytransform).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 nestederror:{...}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; noserverInfo.versionframework leak.MCP-TRANSPORT-STANDARD-v1.md— single stateless/mcp(no 307 split), canonicalserverInfo/ health.- Logging & CLI Standard v1 — structured logging + CLI conventions (canonical text tracked per-repo; no router doc).
Workflow
- Read the standard's Definition of Done; check this repo against it.
- Apply the smallest change that meets the DoD; reuse the router's reference implementation rather than reinventing.
- Add or update the guard test the standard specifies so the change can't regress.
- Run
make ci-local; note residual risk. - 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.
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.
- 9d ago First seen · 29 lines · 46 tokens per session scan A e48d29e1b8cc
fleet-standard-adoption is a skill published in the GitHub repository berntpopp/gencc-link (0 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 510 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to fleet-standard-adoption, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
computase
Performs verified local nucleotide-sequence computation with Computase. Use when an agent needs sequence composition or GC bounds, a reverse complement, translation, candidate ORFs, or IUPAC motif sites through Computase MCP tools or the isolated Skill runner.
noodle-biomedical-literature-discovery
Find, inspect, compare, and traverse public biomedical research literature. Use for PubMed or scholarly paper search, publication details, PMID/DOI/PMCID lookup, related papers, citation paths, semantic literature neighborhoods, corpus coverage, or questions asking what research exists about a gene, variant…
noodle-biomedical-literature-discovery-mcp
Select Noodle Biomedical Literature Discovery MCP from Biorouter for public biomedical paper search, PMID DOI or PMCID lookup, publication inspection, related papers, citation or semantic graph traversal, and corpus metadata even when the user does not know the Noodle name.
biomed-research
Use when answering biomedical research questions that need source-backed evidence from local MCP servers, including gene, disease, drug, variant, phenotype, study, or clinical-trial questions.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.