upstream-protocol-drift-watch
Skill545 starsChanged 9 months agoMITView on GitHub
Dynamically inspect ACP and Codex upstream repos using .agmente.paths, detect protocol/API/spec drift, and produce a risk-scored regression report. Use when checking for new APIs, method changes, or protocol/spec changes after upstream updates.
In this repository13 other files it gives its agents.
- ACPClient/AGENTS.mdAGENTS.md
- Agents.mdAGENTS.md
- Agmente/AGENTS.mdAGENTS.md
- AgmenteTests/AGENTS.mdAGENTS.md
- AgmenteUITests/AGENTS.mdAGENTS.md
- AppServerClient/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- acp-local-runnerSkill
- codex-local-cli-e2eSkill
- repeat-with-delaySkill
- run-agmente-codex-e2eSkill
- run-agmente-e2eSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
If refs are not provided:
- Very specific: line 24
Use HEAD..origin/main for each upstream repo.
- Very specific: line 25
If origin/main is unavailable, use HEAD~1..HEAD.
- Very specific: line 26
If HEAD~1 is unavailable, use HEAD..HEAD and report that no baseline exists.
- Distinctive: line 28
Always fetch upstream remotes before scanning:
- Distinctive: line 35
Read repo-local path registry:
- Distinctive: line 47
Use user-provided refs if given.
- Distinctive: line 49
Always perform git fetch --all --prune before resolving refs and diff range.
- Very specific: line 61
Treat quoted/backticked values like foo/bar as method candidates.
- Distinctive: line 109
Do not write or require a persistent baseline file unless user explicitly asks.
- Distinctive: line 110
Do not create new scripts for this check unless user explicitly asks.
- Distinctive: line 111
Prefer live git state and direct diff inspection each run.
- Distinctive: line 112
Do not skip fetch unless user explicitly asks to avoid network operations.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 --pruneRequired 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
Suggested scoring:
- Path impact (max 70):
- protocol/schema core files changed:
+35each bucket - app-server runtime/docs changed:
+10to+20 - RFD/docs-only changes:
+8to+12
- protocol/schema core files changed:
- Method impact (max 30+):
- added method not recognized locally:
+12each (cap 36) - removed method referenced locally:
+15each (cap 45, immediate high priority) - payload shape changes on core methods (
thread/*,turn/*,session/*): add+10
- added method not recognized locally:
Escalation rule:
- Any removed locally referenced method => at least
medium. - Multiple removed locally referenced methods =>
high.
Output Contract
Always return:
- Summary table: repo, diff range, changed file count, severity, score.
Added unknown methodslist.Removed supported methodslist.- Key changed files likely to affect compatibility.
- Recommended follow-up tests:
swift test --package-path AppServerClientswift test --package-path ACPClient- targeted
AgmenteTestsprotocol suites.
Guardrails
- Do not write or require a persistent baseline file unless user explicitly asks.
- Do not create new scripts for this check unless user explicitly asks.
- Prefer live git state and direct diff inspection each run.
- Do not skip fetch unless user explicitly asks to avoid network operations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

