Borrowing it
Nothing to install: this file belongs to Pseudogiant-xr/Pseudolife-MCP. 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/Pseudogiant-xr/Pseudolife-MCP/master/.claude/skills/merge-forward/SKILL.mdgit clone --depth 1 https://github.com/Pseudogiant-xr/Pseudolife-MCPWrote 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/pseudogiant-xr/pseudolife-mcp/merge-forward)<a href="https://agentmods.dev/skills/pseudogiant-xr/pseudolife-mcp/merge-forward"><img src="https://agentmods.dev/badge/skills/pseudogiant-xr/pseudolife-mcp/merge-forward/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/pseudogiant-xr/pseudolife-mcp/merge-forward"><img src="https://agentmods.dev/badge/skills/pseudogiant-xr/pseudolife-mcp/merge-forward.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.00063 | $0.01305 |
| Opus 5.5 | $0.00025 | $0.00522 |
| Sonnet 5.5 | $0.00013 | $0.00261 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
merge-forward 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merging without fresh CI on the updated head
Ordinary PRs never merge directly: they land through an integrate/*
batch (docs/dev/merge-batches.md), because a push to any other branch
runs only the fast CI lanes. A batch PR normally needs passing CI for its
current head integrated with current master (CLAUDE.md, "Shipping
checklist"). These two exceptions let a batch PR merge on the CI an
earlier head of it passed, after master moved; "the PR" below is that
batch PR and "either side" is the batch against master. Both are to be
removed when the GitHub merge queue is enabled. When in doubt, close the
batch and build the next one.
Merging before CI reports on the new head is a ruleset bypass (admin merge), so only the maintainer or the maintainer's delegate does it.
A. Disjoint merge-forward
Added after #592 waited 25 minutes on a CHANGELOG-only conflict. All of these must hold:
- The previous batch head passed every lane a batch runs:
test,test-lite-linux,test-lite-windows,test-lite-macos,frontend, CodeQL and bothParitygates. The merge-forward commit is the only commit pushed since, since nothing is fixed inside a batch. - The two sides share no file except docs-only files (as CLAUDE.md's
"Docs-only changes" defines them) and
rust/producer-census.json, the census both sides' batches regenerate (item 3). Compute it, don't eyeball it:base=$(git merge-base <previous head> origin/master). Master's set isgit diff --name-only $base..origin/master; the PR's set isgit diff --name-only $base...<previous head>. - No hand resolution outside docs:
git show --remerge-diff --name-only <merge commit>lists only docs-only files.llms-full.txtis regenerated withpython ops/gen_llms_txt.py, never hand-merged.rust/producer-census.jsonis regenerated withpython rust/producer_census.pyin the merge commit whenever the merge changes a file it scans (--checkmust then exit 0), never hand-merged; CI gates every batch and the master push on its currency. - Neither side changes shared ground:
pyproject.toml, lock files or.github/workflows/;tests/conftest.py, fixtures or imported test helpers; schema, DDL or migrations; generated outputs (pseudolife_memory/web/static/). - Neither side's code reaches the other's only through a dynamic import, a subprocess, or HTTP or MCP calls into a daemon whose behaviour the other side changed.
- On the merged head, run locally every test file either side added or
changed since
$base, plus the doc guards and every test naming a touched doc path. All must pass. Read overlapping doc hunks for contradictions; a clean doc auto-merge can still contradict itself.
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 · +5 lines 71b4f51da01c
- 7d ago Changed · +5 lines da070c30e2c2
- 8d ago First seen · 86 lines · 63 tokens per session scan A 480462b20837
merge-forward is a skill published in the GitHub repository Pseudogiant-xr/Pseudolife-MCP (6 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 1,305 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-20.
Other skills, from other repositories
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
pre-pr
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks required tests and docs, then writes Description / Proofs / Fixes.
cartographer-kb-conflict-resolve
Guide an agent through resolving open git rebase conflicts on degraded KB concepts.
commit-pr
Squash the branch into one commit and open or update its pull request (creates a new branch first if on main/master).
bootstrap
Use when resolving Postman CLI setup, authentication, or a repository workspace binding; initializing local API files; handling a CLI error that says an operation isn't allowed because of insufficient entitlements; or importing, pulling, pushing, syncing, or sharing workspace resources. Reuses existing context and…
commit
The ! prefix on each line below runs the shell command inline and injects its output before the prompt is submitted. If the lines below still show the literal commands, this platform does not expand them: run each command yourself first and use its output as the context.