Borrowing it
Nothing to install: this file belongs to anthony-spruyt/claude-plugins. 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/anthony-spruyt/claude-plugins/main/.claude/skills/repo-operator/SKILL.mdgit clone --depth 1 https://github.com/anthony-spruyt/claude-pluginsWrote 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/anthony-spruyt/claude-plugins/repo-operator)<a href="https://agentmods.dev/skills/anthony-spruyt/claude-plugins/repo-operator"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/repo-operator/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/anthony-spruyt/claude-plugins/repo-operator"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/repo-operator.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.00083 | $0.01592 |
| Opus 5.5 | $0.00033 | $0.00637 |
| Sonnet 5.5 | $0.00017 | $0.00318 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
repo-operator 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-operator
repo-operator syncs shared config to its repos with xfg. A synced file is overwritten on every sync, so a change made in the target repo is lost. Change the source in repo-operator.
How xfg works
- Config is
src/in repo-operator:base.yaml(id,deleteOrphaned,prOptions) plus the fragment files named in the table below. content: "@templates/<path>"points atsrc/templates/<path>, resolved relative to the fragment file. Everything distributed lives insrc/templates/.- Groups are named bundles of files and settings and can
extendsother groups. A repo opts in throughgroups:inrepos.yaml. - Conditional groups apply files or settings by which groups a repo has, with
allOf,anyOfandnoneOf. Use them for cross-cutting rules (for example rulesets that differ whenmergifyis present). createOnly: trueseeds a file once and never overwrites it. Use it for files a repo customises (.gitignore,.mega-linter.yml,renovate-overrides.json5). Without it the file is overwritten on every sync.$arrayMerge: appendwith$values: [...]appends to an array (pre-commitrepos, devcontainerextensions). Plain YAML keys replace the array.deleteOrphaned: trueplus the.xfg.jsonmanifest: xfg records what it synced under the configid, and deletes a recorded file from the repos once it leavessrc/.template: truewithvarssubstitutes${xfg:name}and built-ins such as${xfg:repo.fullName}in a file. An unknown variable fails the sync.- xfg substitutes an env reference in any synced content: a dollar sign, a brace, an identifier and a closing brace, with an optional
:-defaultor:?message. An unset one fails the sync. Double the dollar sign ($$before the brace) to emit it literally, aslint.sh.tmpldoes for shell expansions. GitHub expressions and${xfg:...}in a non-template file pass through unchanged. A shell template that holds${xfg:...}takes a.tmplextension (lint.sh.tmpl) so shellcheck skips it. - Comments in YAML/JSON templates are not synced: xfg parses and regenerates them with only the
header:lines fromgroups.yaml. Explain non-obvious config via aheader:link or repo-operator's docs. Shell and markdown templates keep their comments. .github/xfg-managed.jsonmaps each repo to the files xfg overwrites there (notcreateOnlyones)..claude/xfg-managed.shreads it from repo-operator'smain(cached 15 minutes in the git dir). APreToolUsehook blocks Edit, MultiEdit, Write, NotebookEdit and Bash writes to a listed file, and a pre-commit hook refuses commits that change one. Theclaudegroup syncs all three. In repo-operator the root copies are synced too: editsrc/templates/and let Apply write them.
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 · 60 lines · 83 tokens per session scan A f54c002b7f18
repo-operator is a skill published in the GitHub repository anthony-spruyt/claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 1,592 once invoked, about $0.0003 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-13.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.