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 agentic-dev3o/devx-plugins --skill update-origingit clone --depth 1 https://github.com/agentic-dev3o/devx-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/agentic-dev3o/devx-plugins/update-origin)<a href="https://agentmods.dev/skills/agentic-dev3o/devx-plugins/update-origin"><img src="https://agentmods.dev/badge/skills/agentic-dev3o/devx-plugins/update-origin/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/agentic-dev3o/devx-plugins/update-origin"><img src="https://agentmods.dev/badge/skills/agentic-dev3o/devx-plugins/update-origin.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.00052 | $0.01014 |
| Opus 5.5 | $0.00021 | $0.00406 |
| Sonnet 5.5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
update-origin 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 1mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Branch From Origin
Merge origin/<origin-branch> (= $ARGUMENTS, default main) into the current branch, always behind a recoverable backup.
Copy this checklist into your reply and check items off as you go:
Update Progress:
- [ ] Preflight passed (clean tree, not detached, branch ≠ target, push.default safe)
- [ ] Backup branch created
- [ ] Synced with origin/<current-branch> (if it has new commits)
- [ ] Merged origin/<target>
- [ ] Conflicts resolved
- [ ] Result verified clean
- [ ] Pushed (only if user confirmed)
- [ ] Backup deleted (success) or kept (recovery)
Guardrails (exact — do not vary)
- The working tree MUST be clean. Run
git status --porcelain; any output → stop and tell the user to commit or stash first. Do nothing else. - Stop if HEAD is detached or the current branch equals
<origin-branch>. - Back up before touching anything:
git branch backup/$(git branch --show-current)-$(git rev-parse --short HEAD). Tell the user the exact name; call it<backup>below. - Never delete
<backup>unless the final tree is verified clean and the update succeeded. - Never rebase, never force-push (
--force,--force-with-lease,+refspec— all forbidden). Several developers and agents work on the same branch; rewriting published history clobbers their work. A rejected push means new remote commits to merge in, never to overwrite. - Push only the current branch — never a bare push. A bare
git pushobeyspush.default, and undermatchingit pushes every same-named local branch. Alwaysgit push origin HEAD. Preflight hardening: rungit config push.default; ifmatchingor empty, warn the user and offergit config push.default currentfor this repo.
Phase 1 — Sync and merge
git fetch origin.- If
origin/<current-branch>exists and has commits not on HEAD (git rev-list --count HEAD..origin/<current-branch>> 0), others pushed while you worked →git merge origin/<current-branch>first. git merge origin/<origin-branch>.
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.
- 1mo ago First seen · 70 lines · 52 tokens per session scan A c020edd8a76c
update-origin is a skill published in the GitHub repository agentic-dev3o/devx-plugins (12 stars, last pushed 10d ago), licensed MIT. It adds 52 tokens to every session and 1,014 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.