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 hxy91819/mason-skills --skill open-source-fork-maintenancegit clone --depth 1 https://github.com/hxy91819/mason-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/hxy91819/mason-skills/open-source-fork-maintenance)<a href="https://agentmods.dev/skills/hxy91819/mason-skills/open-source-fork-maintenance"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/open-source-fork-maintenance/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/hxy91819/mason-skills/open-source-fork-maintenance"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/open-source-fork-maintenance.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.00020 | $0.00590 |
| Opus 5 | $0.00010 | $0.00295 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
open-source-fork-maintenance 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 today.
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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open-source fork maintenance
This is a process skill. Invoke it explicitly as $open-source-fork-maintenance when maintaining a public upstream fork whose operator cannot merge changes upstream. It establishes and operates a local local/aggregate integration branch without treating it as an upstream contribution branch.
Boundary
Use this skill only after confirming that the repository is a public fork or upstream clone and that the operator is not an upstream maintainer. Upstream maintainers should use the project's normal contribution and release workflow instead.
The project owns its branch registry, its feedback records, its verification commands, and any local service deployment. The skill owns the repeatable maintenance model:
- the main checkout stays on
local/aggregatefor integration and experience; - every product change lives on its own
feature/*orfix/*branch and worktree; - a source branch is verified after relevant project checks pass in its worktree and
$autoreviewcloseout there reports no accepted/actionable findings; - the aggregate receives verified source commits with
git cherry-pick -x; - a committed project manifest records each source commit, aggregate commit, and upstream feedback issue.
The personal fork is the handoff channel: after verified packaging, push each completed source branch and local/aggregate to that fork with ordinary fast-forward pushes. Those published aggregate commits are reusable source snapshots for another environment, never upstream contribution branches.
Read references/setup.md before initializing a repository. Initialization creates branches, project files, and a project-local skill link, so perform it only after the user explicitly authorizes setup.
For an already initialized fork, read references/maintenance.md. Run the linked scripts/local-aggregate-status.mjs from the project root after fetching the configured upstream. It reports source-branch changes, unregistered local feature/fix branches, upstream changes, stable releases when configured, and the state of every registered upstream feedback issue.
What ships with it
10 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.
- agents/openai.yaml 43 B
- assets/AGENTS.local-aggregate.md 2.1 KB
- assets/local-aggregate-features.json 237 B
- metadata.yaml 120 B
- references/maintenance.md 3.8 KB
- references/setup.md 3.7 KB
- scripts/link_project_skill.py 2.9 KB runs code
- scripts/local-aggregate-status.mjs 17 KB runs code
- tests/test_link_project_skill.py 3.2 KB runs code
- tests/test_local_aggregate_status.mjs 5.1 KB runs code
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.
- today Changed · +2 lines efa61a3b29f8
- yesterday Changed · +3 lines be25df0707bf
- 2d ago First seen · 31 lines · 20 tokens per session scan A 4224139a4e10
open-source-fork-maintenance is a skill published in the GitHub repository hxy91819/mason-skills (2 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 590 once invoked, about $0.0001 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-09-10.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…