Borrowing it
Nothing to install: this file belongs to loerei/chronicle-mcp. 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/loerei/chronicle-mcp/main/.agents/skills/review-upstream/SKILL.mdgit clone --depth 1 https://github.com/loerei/chronicle-mcpWrote 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/loerei/chronicle-mcp/review-upstream)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/review-upstream"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/review-upstream/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/loerei/chronicle-mcp/review-upstream"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/review-upstream.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.00030 | $0.00534 |
| Opus 5 | $0.00015 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
review-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 10d 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
Review Upstream Skills
Fetch, diff, and reconcile custom skill updates from upstream source repositories into myskills/.
Workflow
flowchart TD
Start["Trigger: /review-upstream"] --> Fetch["1. Fetch: node sync-upstream.js --all"]
Fetch --> Triage{"2. Triage Skills"}
Triage -->|"New Skill"| AskNew["Ask user: Add to official catalog?"]
Triage -->|"Modified Skill"| DiffCheck["Compare local vs upstream diff & recommend action"]
AskNew -->|"Approved"| ApplyAdd["node sync-upstream.js --apply <name> --action add --category <cat>"]
DiffCheck --> Choice{"User Decision"}
Choice -->|"Overwrite"| ApplyOverwrite["node sync-upstream.js --apply <name> --action overwrite"]
Choice -->|"Keep Local"| Skip["Skip apply"]
Choice -->|"Combine"| ManualMerge["Manually edit local SKILL.md"]
ApplyAdd --> Cleanup["3. Clean pending: node sync-upstream.js --clear"]
ApplyOverwrite --> Cleanup
Skip --> Cleanup
ManualMerge --> Cleanup
Cleanup --> Sync["4. Sync: agents audit -a -p && agents distribute"]
Sync --> Git["5. Commit & Push myskills"]
CLI Reference
| Action | Command |
|---|---|
| Fetch all upstream | node sync-upstream.js --all |
| Apply new skill | node sync-upstream.js --apply <skill_name> --action add --category <category> |
| Overwrite local skill | node sync-upstream.js --apply <skill_name> --action overwrite |
| Clear pending queue | node sync-upstream.js --clear |
| Audit & Distribute | agents audit -a -p && agents distribute |
Triage Rules for Modified Skills
For each modified skill, report to the user:
- Summary of differences: What upstream added vs. what local customized.
- Recommendation: State clearly whether to overwrite, keep local, or merge.
- Options:
a. Keep local(reject upstream changes)b. Overwrite(accept upstream version)c. Merge(manually combine complementary improvements)
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.
- 10d ago First seen · 55 lines · 30 tokens per session scan A c74cb97bc391
review-upstream is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 534 once invoked, about $0.0002 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…