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 varutasu/agent-pipeline --skill sync-agent-contextgit clone --depth 1 https://github.com/varutasu/agent-pipelineWrote 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/varutasu/agent-pipeline/sync-agent-context)<a href="https://agentmods.dev/skills/varutasu/agent-pipeline/sync-agent-context"><img src="https://agentmods.dev/badge/skills/varutasu/agent-pipeline/sync-agent-context/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/varutasu/agent-pipeline/sync-agent-context"><img src="https://agentmods.dev/badge/skills/varutasu/agent-pipeline/sync-agent-context.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.00134 | $0.02924 |
| Opus 5.5 | $0.00054 | $0.01170 |
| Sonnet 5.5 | $0.00027 | $0.00585 |
| Haiku 4.5 | $0.00013 | $0.00292 |
Grade A, and why
sync-agent-context 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 2mo 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Agent Context
Compares this repo's installed agent-pipeline artifacts against the canonical pipeline source. Surfaces drift. Lets the user accept or reject each update file-by-file. Updates the manifest. Never auto-commits.
Trigger phrases
- "Sync agent context for this repo."
- "Check for agent-pipeline updates."
- "Update the L2 roles from the latest pipeline."
- "Am I on the latest agent-pipeline?"
- "Refresh
.cursor/agents/from the pipeline."
Inputs
.agent-context-manifest.ymlat the current repo root (REQUIRED; if missing, runbootstrap-agent-contextfirst OR offer to generate a retroactive manifest — see Step 1b).- The pipeline repo, located by following the symlink at
~/.cursor/skills/bootstrap-agent-context. The skill source path is the pipeline repo root +/skills/bootstrap-agent-context, so the pipeline root is two levels up.
Outputs
- A drift report printed to chat — table of
path | state | action. - File contents updated in place for artifacts the user accepted.
.agent-context-manifest.ymlrewritten with new versions / hashes /last_synced_at.- A hand-off message: "Sync complete. N files updated, M files held back. Review the diff and commit."
The skill NEVER runs git add, git commit, or any side-effect command. It writes files and stops.
Hard rules
- Never silently overwrite a customized file. If
installed_hashdoesn't match the file's current hash, the user owns that file. Show a 3-way diff (manifest hash → current → pipeline) and ask. - Never delete files from the consumer repo. Out-of-pipeline artifacts (e.g. user-added rules) are left alone.
- Never re-bootstrap. If layers in the pipeline have grown (e.g. a new role file was added upstream), surface the new files as additions the user can opt into; don't write them automatically.
- Always update
last_synced_atat the end, even if no files changed (so the user can see when the last check ran).
Steps
Step 0: Locate the pipeline repo
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.
- 2mo ago First seen · 222 lines · 134 tokens per session scan A 50f80825d747
sync-agent-context is a skill published in the GitHub repository varutasu/agent-pipeline (2 stars, last pushed 2mo ago), licensed MIT. It adds 134 tokens to every session and 2,924 once invoked, about $0.0005 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-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…