upstream-contribution skillA
upstream-contribution is agent-read markdown (skill) from jakeselby/agent-harness: Contribute from a fork to a repository you do not own without burning maintainer trust. Use when the working repo has an `upstream` remote, when the user says "open a PR against <someone else's repo>", or before the first commit in any repo the user is a guest in..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Upstream contribution **This repo is not yours.** It belongs to its maintainers, with their own queue, their own conventions and their own history of unmerged good intentions. Act like a guest. ## Remotes `origin` is **your fork**. `upstream` is the project, and its push URL is set to `no_push`: ```bash git remote set-url --push upstream no_push git remote -v # origin = fork, upstream = project (no_push) ``` The remote you type by reflex is the one that is safe to push to. **Never commit to local `main`** — keep it a clean mirror of upstream so rebases stay trivial: ```bash git fetch upstream && git checkout main && git reset --hard upstream/main ``` ## Issue before code For anything larger than a bug fix or a doc correction, **open an issue and wait for a maintainer response before writing the implementation.** Most projects have a graveyard of large unsolicited PRs. Volume of code is not what gets merged; agreement beforehand is. Use the repo's issue templates. If the work is speculative, say so. ## Branch and PR scope - Branch names: `<issue-number>-brief-description` when an issue exists, otherwise `<area>-brief-description`. …
Read the whole file at its exact version.
How to install
mdr add jakeselby/agent-harness/upstream-contribution@git:20260923.097bdb0mdr add jakeselby/agent-harness/upstream-contribution@sha256:e1c32df9cdfc6a42Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_hagyopppdustx4gx)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.097bdb0 latest | 2026-09-23 | 097bdb0 | 2,939 B | A | view · diff |
| git:20260919.6cf18f7 | 2026-09-19 | 6cf18f7 | 3,012 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2939 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jakeselby/agent-harness · 17 stars · license MIT · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hagyopppdustx4gx GET https://markdownregistry.com/api/v1/resolve?ref=jakeselby/agent-harness/upstream-contribution GET https://markdownregistry.com/api/v1/blob/e1c32df9cdfc6a4266fe5840a329fa80cb4d205231cc929d1e7a2f9e8c626088
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.