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 Kestral-Team/kestral-plugins --skill kestral-syncgit clone --depth 1 https://github.com/Kestral-Team/kestral-pluginsWrote 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/kestral-team/kestral-plugins/kestral-sync)<a href="https://agentmods.dev/skills/kestral-team/kestral-plugins/kestral-sync"><img src="https://agentmods.dev/badge/skills/kestral-team/kestral-plugins/kestral-sync.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.00044 | $0.00628 |
| Opus 5 | $0.00022 | $0.00314 |
| Sonnet 5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
kestral-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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kestral Sync
Keep the linked Kestral task in sync with this coding session. Full playbooks live on the server and are returned by the MCP operation — do not invent sync procedures from memory.
How to sync
Call:
execute_operation("sync_session_workflow", { intent })
| Intent | When |
|---|---|
session_start |
Beginning of a linked-repo session (hooks do this) |
pickup |
Starting work on a task |
update |
Progress, review, status, comments |
create |
Explicitly creating a task for current work |
update_or_create |
Prefer sync_after_push after push/PR instead |
repo_opt_in |
Resolving home auto-sync prefs for this folder |
Optional workType: omit or "coding" (default) for branch/PR/milestone playbooks; "general" for non-coding
comment/status/create (no branch/PR).
Follow the returned instructions and call listed ops by operationId. Do not call search_operations first for
sync/pickup/push.
After push / PR
Prefer one call:
execute_operation("sync_after_push", { branchName, summary?, prUrl? })
Do not run Full Sync afterward.
Opt out of GitHub auto-link / auto-create
For chore or one-off work with no Kestral task, call
execute_operation("set_pr_tracking", { tracked: false, branchName, prUrl? }) as soon as the branch is known (before
the PR exists). Fall back to <!-- kestral:skip-auto-link --> in the PR body only if MCP is unavailable. To undo an
auto-created task: pass removeAutoCreatedTask: true with prUrl.
Never write MCP into product code
execute_operation / MCP tool calls are agent-session actions only. Never write them into application source.
When to sync
- After
git push,gt submit, orgh pr create - Structured plan written — offer tracking tasks; ask one parent for the plan vs a task per phase/deliverable
(
intent: createif approved) - Phase or feature complete
- PR created or linked
- Review, bugfix, or prototype conclusion
- User asks to sync
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 73 lines · 44 tokens per session scan A 5b46ba2c9eb9
kestral-sync is a skill published in the GitHub repository Kestral-Team/kestral-plugins (4 stars, last pushed 19d ago), licensed Apache-2.0. It adds 44 tokens to every session and 628 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.