Borrowing it
Nothing to install: this file belongs to julien777z/agent-sync-action. 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/julien777z/agent-sync-action/main/.agents/skills/propagate-skill/SKILL.mdgit clone --depth 1 https://github.com/julien777z/agent-sync-actionWrote 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/julien777z/agent-sync-action/propagate-skill)<a href="https://agentmods.dev/skills/julien777z/agent-sync-action/propagate-skill"><img src="https://agentmods.dev/badge/skills/julien777z/agent-sync-action/propagate-skill.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.00071 | $0.02138 |
| Opus 5 | $0.00036 | $0.01069 |
| Sonnet 5 | $0.00014 | $0.00428 |
| Haiku 4.5 | $0.00007 | $0.00214 |
Grade A, and why
propagate-skill 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- propagate-skill — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propagate Skill Changes
Build one canonical repository-neutral agent contract, preserve repository-specific guidance, and delegate all repository-wide execution mechanics to coordinate-repositories.
Dependencies
coordinate-repositories— own scope, repository lifecycle, mutation safety, conflict repair, and completion verification.code-simplify— equip every propagated repository for mandatory implementation simplification.
Skill Listing
When the invocation names no skill or rule other than propagate-skill as the workflow trigger, list every canonical skill found at .agents/skills/*/SKILL.md as an alphabetized Markdown bullet list, then stop. Do not discover repositories or mutate files for a listing-only invocation.
User-Level Installations
During an authorized change-propagation run whose selected scope includes repository consumers, also converge every matching skill that already exists in a writable user-level skill root exposed by the active host or its configured skill catalog. Do this whether repository consumers need edits or are already current; the mutation run and selected repository scope are the trigger, not whether a repository diff happens to be produced. Resolve real paths and ownership before classifying a target. Never infer user scope by broadly crawling a home directory, and exclude project, system, plugin, provider-managed, generated, and read-only installations.
Do not install a missing user-level skill. For each existing editable match, treat the selected canonical skill directory as the source for canonical-managed files, compare the complete installation, and apply the same semantic-classification and deletion-ledger rules used for repository consumers. Preserve compatible local additions other than provider metadata. Never compare, copy, create, or refresh agents/openai.yaml; remove an existing local copy only with explicit deletion authorization.
Delegate snapshots, filesystem mutation, typed manifest state, independent verification, and recovery to coordinate-repositories. Listing and other read-only runs never mutate user-level installations.
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.
- 8d ago First seen · 64 lines · 71 tokens per session scan A a9ebbf60aa2f
propagate-skill is a skill published in the GitHub repository julien777z/agent-sync-action (5 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 2,138 once invoked, about $0.0004 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…