Borrowing it
Nothing to install: this file belongs to rebornix/Agmente. 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/rebornix/Agmente/main/.agents/skills/upstream-protocol-drift-watch/SKILL.mdgit clone --depth 1 https://github.com/rebornix/AgmenteWrote 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/rebornix/agmente/upstream-protocol-drift-watch)<a href="https://agentmods.dev/skills/rebornix/agmente/upstream-protocol-drift-watch"><img src="https://agentmods.dev/badge/skills/rebornix/agmente/upstream-protocol-drift-watch/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/rebornix/agmente/upstream-protocol-drift-watch"><img src="https://agentmods.dev/badge/skills/rebornix/agmente/upstream-protocol-drift-watch.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.00907 |
| Opus 5 | $0.00028 | $0.00453 |
| Sonnet 5 | $0.00011 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
upstream-protocol-drift-watch 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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upstream Protocol Drift Watch
Goal
Catch upstream ACP/Codex changes early, especially:
- new RPC/API methods,
- removed or renamed methods,
- protocol/spec file changes that can cause Agmente regressions.
This skill is dynamic by default: always read current local repos and refs at runtime.
Inputs
Collect these from the user request when present:
- optional
from_refandto_ref(for each repo, or shared), - whether to check
codex,acp, or both.
If refs are not provided:
- Use
HEAD..origin/mainfor each upstream repo. - If
origin/mainis unavailable, useHEAD~1..HEAD. - If
HEAD~1is unavailable, useHEAD..HEADand report that no baseline exists.
Always fetch upstream remotes before scanning:
git -C <repo> fetch --all --prune
Required Runtime Sources
- Read repo-local path registry:
cat .agmente.paths
- Resolve:
AGMENTE_CODEX_REPOAGMENTE_ACP_REPO
- Validate both paths are git repos before scanning.
Dynamic Scan Workflow
- Resolve diff range per repo.
- Use user-provided refs if given.
- Otherwise use
HEAD..origin/main. - Always perform
git fetch --all --prunebefore resolving refs and diff range.
- Collect changed files in protocol-relevant areas.
- Codex focus paths:
codex-rs/app-server-protocolcodex-rs/app-server
- ACP focus paths:
docs/schemadocs/protocoldocs/rfds
- Extract method-like token changes from patch.
- Treat quoted/backticked values like
foo/baras method candidates. - Track added and removed candidates separately.
- Compare against locally supported methods.
- Codex local method sources:
AppServerClient/Sources/AppServerClient/AppServerMethods.swiftAppServerClient/Sources/AppServerClient/AppServerEventParser.swift
- ACP local method sources:
ACPClient/Sources/ACPClient/ACP/ACPMethods.swiftACPClient/Sources/ACPClient/ACP/ResponseDispatcher.swift
- Build a risk score and severity.
Risk Scale
0-19: none20-44: low45-74: medium75-100: high
What ships with it
1 file 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.
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.
- 9d ago First seen · 113 lines · 57 tokens per session scan A 83f81fa6c88b
upstream-protocol-drift-watch is a skill published in the GitHub repository rebornix/Agmente (542 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 907 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.