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 richfrem/agent-plugins-skills --skill os-lab-backportgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/richfrem/agent-plugins-skills/os-lab-backport)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/os-lab-backport"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/os-lab-backport/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/richfrem/agent-plugins-skills/os-lab-backport"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/os-lab-backport.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.00139 | $0.00680 |
| Opus 5.5 | $0.00056 | $0.00272 |
| Sonnet 5.5 | $0.00028 | $0.00136 |
| Haiku 4.5 | $0.00014 | $0.00068 |
Grade A, and why
os-lab-backport 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 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.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lab Backport Reviewer (os-lab-backport)
Reviews changes from an experimental lab repo and backports approved modifications to master plugin sources in agent-plugins-skills.
Contents
Critical Constraints
- No Blind Copies: Understand the rationale and eval score delta behind each lab change before applying.
- Hub-First Updates: Edit only canonical sources in the master plugin (
plugins/<plugin>/in the master repo); spokes are managed symlinks. - Preserve Valid Constraints: Never backport changes that remove or weaken safety guards.
Quick start
Inspect the git diff of the lab repository against its baseline:
git -C <lab-repo-path> diff <baseline-commit> HEAD
Workflow
- Intake & Scope: Determine lab repo path, master plugin path, and baseline commit SHA.
- Progress Audit: Read
<lab-repo>/LOG_PROGRESS.mdand check evaluation logs. - Assess Diff: Classify changed files as
ACCEPT,ADAPT,REJECT, orREVIEW. - Apply Approved Changes: Apply targeted diffs to the master plugin sources.
- Log & Debrief: Persist the run with
os-lab-log, then record operational learnings viaos-lab-memory.
Verification
Run test suites and audits against modified master plugin sources:
git diff plugins/<plugin>/
References
- detailed-reference.md — Intake questions, assessment table formats, and source mapping.
- phase-guide.md — Phase-by-phase backport guide.
- acceptance-criteria.md — Backport criteria and verification standards.
- fallback-tree.md — Remediation pathways when lab diffs conflict or fail tests.
Diagrams: assets/diagrams/os-lab-backport-phases.mmd and assets/diagrams/os-lab-backport-sequence.mmd.
What ships with it
9 files 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.
- assets/diagrams/os-lab-backport-phases.mmd 54 B
- assets/diagrams/os-lab-backport-sequence.mmd 56 B
- assets/diagrams/sibling-repo-labs.mmd 49 B
- evals/evals.json 918 B
- evals/results.tsv 172 B
- references/acceptance-criteria.md 58 B
- references/detailed-reference.md 57 B
- references/fallback-tree.md 52 B
- references/phase-guide.md 61 B
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 First seen · 66 lines · 139 tokens per session scan A b5af09e38c1e
os-lab-backport is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed 2d ago), licensed MIT. It adds 139 tokens to every session and 680 once invoked, about $0.0006 per session on Opus 5.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-10-16.
Other skills, from other repositories
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.
review-open-pull-requests
List and analyze all open pull requests across GitHub repositories. Shows review status, CI/CD check results, age, and reviewers. Use when triaging PRs, checking team velocity, or identifying stale reviews that need attention.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
github-pr-review
Review one exact GitHub pull-request head from bounded changed-file patches and check evidence, producing source-line findings without posting or claiming tests ran.
collaboration
Guide for collaborating on GitHub projects. This skill should be used when contributing to projects, creating PRs, reviewing code, or managing issues on GitHub.
ai-driven-code-editor-cli
OpenCode AI - AI-driven code editor/IDE (CLI/TUI version of Cursor/Windsurf). Use when: (1) AI-assisted coding tasks, (2) Code refactoring with AI, (3) GitHub PR review/fixes, (4) Multi-file edits requiring context, (5) Running AI agents on codebases. NOT for: simple one-line ed…