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 conn-castle/agent-layer --skill skill-syncgit clone --depth 1 https://github.com/conn-castle/agent-layerWrote 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/conn-castle/agent-layer/skill-sync)<a href="https://agentmods.dev/skills/conn-castle/agent-layer/skill-sync"><img src="https://agentmods.dev/badge/skills/conn-castle/agent-layer/skill-sync/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/conn-castle/agent-layer/skill-sync"><img src="https://agentmods.dev/badge/skills/conn-castle/agent-layer/skill-sync.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.00063 | $0.00944 |
| Opus 5.5 | $0.00025 | $0.00378 |
| Sonnet 5.5 | $0.00013 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
skill-sync 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 1mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Sync
Use this skill to import known skills from Git and manage them over time. Users can edit imported skills locally, pull upstream updates without overwriting those edits, pin imports to a chosen version, reset them to upstream, or publish changes back.
Use live al skills --help and subcommand help as the source of truth. If al
is unavailable or the project is not initialized, stop and report the error.
Do not replace an al skills operation with manual file edits.
There is no al skills sync command. Use al skills pull to update skills from
Git. Use al sync only to copy the current local skills into enabled client
directories.
- Start with
al skills status --all. It reads local state without using the network. Aconflictedskill includes its Git workspace path. - To compare live trees, run
al skills diff <name>with--from/--tobase,local,upstream, ordestination. Defaults are local to upstream. The output is an ordinary Git unified diff. - To import skills, run
al skills add <repository> <selector>... --yesonly when the user explicitly requests the import and the repository and selectors are known. Quote selectors that contain wildcards or start with!. The command does not search for, recommend, or preview skills. Runal skills add --helpbefore choosing source, tracking, or publishing options. - To update imported skills, run
al skills pull. It fetches every configured source and merges upstream changes with local edits. Pinned imports stay at their locked versions unless their configuredrefchanges. Treat any partial or conflicted result as a failure and report every result. For a conflict, finish the Git merge in the workspace named in the error,git addthe result, then runal skills resolve <name>. Do not hand-edit the lockfile. - To stop managing one selector, run
al skills remove <repository> <selector> --yesonly when the user explicitly requests the removal, using the exact values from.agent-layer/config.toml. Skills still matched by another selector remain managed. Clean skills that are no longer matched are deleted. If one has local edits, the command fails and preserves it. Removing an exclusion may import newly included skills.
Edit an imported skill only in .agent-layer/skills-imported/<skill-name>/. Do
not edit the generated copies under .agents/skills/ or .claude/skills/. The
al sync command replaces them.
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.
- 1mo ago First seen · 77 lines · 63 tokens per session scan A c059c06dfbdb
skill-sync is a skill published in the GitHub repository conn-castle/agent-layer (10 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 944 once invoked, about $0.0003 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
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
apply-patch
Apply multi-file or tricky edits atomically with git apply instead of many fragile editfile calls. Use when changing several files at once or when editfile fails to match.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-ref-git-workflow
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
commit
Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.