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-contextgit 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-context)<a href="https://agentmods.dev/skills/kestral-team/kestral-plugins/kestral-context"><img src="https://agentmods.dev/badge/skills/kestral-team/kestral-plugins/kestral-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/kestral-team/kestral-plugins/kestral-context"><img src="https://agentmods.dev/badge/skills/kestral-team/kestral-plugins/kestral-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.00047 | $0.01921 |
| Opus 5 | $0.00023 | $0.00960 |
| Sonnet 5 | $0.00009 | $0.00384 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
kestral-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 9d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Search your Kestral workspace and pull relevant documents, projects, and tasks into the conversation. This gives the agent real workspace knowledge so it can answer questions like "what's the latest on the auth migration?" without you having to paste anything.
Prerequisites
The Kestral MCP server must be in this session (/mcp). Authentication is handled by the MCP connection (OAuth) —
proceed directly with operations. If any call returns auth failure (401, unauthorized, or Not authenticated), ask the
user to reconnect or authenticate through their app's UI (Cowork: Customize → Connectors; Codex: authenticate then
start a new thread using /new — CLI: codex mcp login Kestral; app: Plugins → Kestral → MCP servers gear; Claude Code: /mcp →
reconnect).
Human-readable references
Keep Kestral IDs internal unless the user asks for them. In user-facing output:
- Tasks: show
slug - titlewhen a slug is available, linked withurlwhen the host can render links. - Projects, documents, feedback, customers, tags, statuses, and other Kestral entities: show the readable
name/title/label first, linked with
urlwhen the host can render links. - People and actors: show display names; if unresolved, write
Unknown member (id: <rawId>). - Unknown non-member entities: write
Unknown <entity type> (id: <rawId>). - Approval tables and write-back plans must put the human-readable label first. Raw URLs, machine IDs, source IDs, and bare slugs belong only in secondary metadata when useful.
- Use existing display fields first; do extra lookups only for entities that matter to the answer.
Workflow
1. Get the query
The user's prompt after /kestral:context is the search topic. Examples:
/kestral:context auth migration/kestral:context what do customers say about onboarding?/kestral:context project roadmap for Q3
If the prompt is empty, ask: "What topic should I search for in your Kestral workspace?"
2. Search across entity types
What ships with it
1 file 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.
- 9d ago First seen · 192 lines · 47 tokens per session scan A 3f6ced12cca1
kestral-context is a skill published in the GitHub repository Kestral-Team/kestral-plugins (4 stars, last pushed 20d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,921 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.