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 AtlasOmnia/donna-starter --skill stale-patch-reconciliationgit clone --depth 1 https://github.com/AtlasOmnia/donna-starterWrote 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/atlasomnia/donna-starter/stale-patch-reconciliation)<a href="https://agentmods.dev/skills/atlasomnia/donna-starter/stale-patch-reconciliation"><img src="https://agentmods.dev/badge/skills/atlasomnia/donna-starter/stale-patch-reconciliation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.02146 |
| Opus 5 | $0.00013 | $0.01073 |
| Sonnet 5 | $0.00005 | $0.00429 |
| Haiku 4.5 | $0.00003 | $0.00215 |
Grade A, and why
stale-patch-reconciliation scanned grade A with 1 finding 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Running `./.venv/bin/python -m pytest` from a gateway session can trip the terminal tool's lifecycle guard — `ValueError: embedded null byte` in `cron/lifecycle_guard.py`, triggered whenever the command's FIRST EXECUTA Copies of this mod
1 near-identical copy found in the catalogue:
- stale-patch-reconciliation — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stale Patch Reconciliation
Use when a patch/diff must be compared with, repaired against, or refreshed for a moving checkout — "is this patch still needed", "does upstream already contain it", "what changed since it was written", "reconcile X.diff with HEAD", or "make apply-patches pass again".
This skill has two explicit modes:
- Analysis mode (default): read-only archaeology and a minimal repair plan. Do not edit, reset, stash, clean, update, or restart.
- Repair mode (only when authorized): implement the invariant in an isolated worktree, run focused gates, regenerate the patch from the current baseline and an explicit file allowlist, then apply it to the live checkout only after clean/reverse checks pass. Preserve unrelated dirty work exactly.
Deliverable shape: (1) behavioral invariant, (2) exact gaps/call sites, (3) upstream status, (4) drift cause, (5) minimal repair, (6) focused gate evidence, and (7) artifact/applicator verification. Coordinate writer ownership through shared-worktree-agent-orchestration.
Core sequence
-
Read the full patch first. Paginate the whole diff; note every file touched and the old-file line numbers of each hunk. The hunks are the map for later drift attribution.
-
Git history archaeology — does the feature exist anywhere?
git log --all --oneline -i --grep=<feature>— commits mentioning it by namegit log --all --oneline -S'<feature>'— commits adding/removing the string (catches renames/variants)git log origin/main -S'<feature>'— empty means NOT upstream (private branches don't count as upstream)git merge-base --is-ancestor <sha> HEAD && echo YES || echo NO— ancestry testgit branch -a --contains <sha>— which branches carry the commits
- Snapshot-branch trap. If
git merge-base HEAD <branch>returns EMPTY output, the branch is likely built on a parentless snapshot commit. Confirm withgit log --format='%h parents: %P' -1 <sha>— no parents = root/snapshot commit (e.g. "chore: snapshot upstream main for private feature review"). Such a branch shares NO ancestry with HEAD, so lineage tools mislead; treat the branch's cumulative diff as the feature and ignore ancestry.
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.
- 4d ago First seen · 69 lines · 26 tokens per session scan A 9e7144820c38
stale-patch-reconciliation is a skill published in the GitHub repository AtlasOmnia/donna-starter (107 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 2,146 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
dependency-update-bot
Scans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated…
explain-this-pr
Takes a GitHub PR URL or the current branch and writes a plain-English explanation of what it does and why, then posts it as a PR comment. Use when asked to explain a PR, summarize a pull request, write a plain-English description of a PR, add a summary comment to a PR, or understand what a PR changes. Trigger when a…
pr-description-writer
Use when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch. Reads the branch diff and commit messages, writes a structured PR body (summary, changes, testing), and optionally creates or updates the PR via the gh CLI.
github-pages-portfolio
Build, update, and verify a single-page static portfolio / intro site on GitHub Pages (pure HTML+CSS+JS, no build step). Covers sourcing content read-only from the user's existing GitHub repos (public AND private), the free-tier public-repo requirement, anchor+accordion single-page design (hidden content revealed on…
git-conventional-commits
Author standardized conventional commit messages (feat, fix, docs, refactor, chore), generate automated semver releases, and format pull request descriptions.
github-profile-readme
Build or rewrite a GitHub profile README (the username/username special repo) with a personalized theme — animated SVG banner, stats cards, contribution snake, tech badges, project/research tables. Includes the git conflict pitfall when the local clone is stale vs GitHub web edits, and the PyYAML on: quirk for…