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 agentmods add skills/jerrylalala/compound-engineering/ce-sync-upstreamnpx skills add Jerrylalala/compound-engineering --skill ce-sync-upstreamgit clone --depth 1 https://github.com/Jerrylalala/compound-engineeringWrote 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/jerrylalala/compound-engineering/ce-sync-upstream)<a href="https://agentmods.dev/skills/jerrylalala/compound-engineering/ce-sync-upstream"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/ce-sync-upstream.svg" alt="Measured on agentmods" 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.00028 | $0.00651 |
| Opus 5 | $0.00014 | $0.00326 |
| Sonnet 5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
ce:sync-upstream 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 5d 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.
What it actually says
Upstream Sync Detection Command
一键检测多个上游仓库最近 30 天的更新，通过角色化策略获取数据，过滤噪音，生成带 YAML frontmatter 的结构化报告供用户决策是否整合。
参数说明
| 参数 | 说明 | 示例 |
|---|---|---|
[F] |
强制全量扫描（v1 无实际差异，保留为未来缓存接口） | /ce:sync-upstream [F] |
Main Tasks
Phase 0: 参数解析与前置条件
检测 [F] 标志：如果包含 [F] 或 [f] → FULL_SCAN = true，从参数中移除。
前置条件验证：
ghCLI:gh auth statusupstreamremote:git remote get-url upstream
失败不中断整体流程，仅对相关仓库标记 status=failed。
Phase 1: 配置加载与数据获取
1.1 读取配置
读取 docs/sync-reports/upstream-repos.json。如不存在，使用默认 4 仓库配置创建。
1.2 并行获取数据
计算 30 天前日期：
powershell -c "(Get-Date).AddDays(-30).ToString('yyyy-MM-ddTHH:mm:ssZ')"
对每个仓库根据 strategy 并行执行：
git-native (parent): git fetch upstream main --no-tags → git log --since="30 days ago" HEAD..upstream/main
github-api (reference): gh api repos/{owner}/{repo}/releases + gh api repos/{owner}/{repo}/commits
releases (runtime): gh api repos/{owner}/{repo}/releases
Phase 2: 噪音过滤与分析
排除：^chore、^bump、dependabot、^Merge pull request、^Merge branch
对每个变更评估相关性（高/中/低），必须附理由。
Phase 3: 报告生成
写入 docs/sync-reports/YYYY-MM-DD-upstream-sync.md，包含 YAML frontmatter + 摘要表格 + 详细分析 + 整合建议优先级。
Phase 4: 讨论
使用 AskUserQuestion：
"报告已生成。发现 N 个相关更新。下一步？"
- 逐项讨论 — 对高相关变更逐个评估
- 创建整合计划 — 运行
/ce:plan - 执行上游合并 —
git merge upstream/main --squash - 稍后处理 — 结束流程
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.
- 5d ago First seen · 71 lines · 28 tokens per session scan A 24898bbd7339
ce:sync-upstream is a skill published in the GitHub repository Jerrylalala/compound-engineering (5 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 651 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…