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 agentmods add skills/muratsilahtaroglu/claude-code-starter-kit/keel-continuenpx skills add muratsilahtaroglu/claude-code-starter-kit --skill keel-continuegit clone --depth 1 https://github.com/muratsilahtaroglu/claude-code-starter-kitWrote 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/muratsilahtaroglu/claude-code-starter-kit/keel-continue)<a href="https://agentmods.dev/skills/muratsilahtaroglu/claude-code-starter-kit/keel-continue"><img src="https://agentmods.dev/badge/skills/muratsilahtaroglu/claude-code-starter-kit/keel-continue.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 | $0.00000 | $0.02586 |
| Opus 5 | $0.00000 | $0.01293 |
| Sonnet 5 | $0.00000 | $0.00517 |
| Haiku 4.5 | $0.00000 | $0.00259 |
Grade A, and why
keel-continue 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 today.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/keel-continue — decide what this session does next, then do it
When: at session start, after a compaction, after --resume, when a message from another session
wakes this one, or any time "what should I be doing?" needs an ACTIVE answer. The SessionStart hook
only REMINDS you what to re-read; this skill does the reading, cross-checks it against reality (git),
and ends in exactly one of three verdicts.
(Renamed from /keel-start in v0.8.28: it answers more than "how do I start" — resuming, taking new
work, and going idle are the same decision, taken from the same evidence.)
Read-only in a worker/solo session — it writes no file there, so EVERY session type may run it: owner, developer, co-agent (rules §10.42 walls co-agents off the WRITE rituals; this isn't one). The ORCHESTRATOR branch (§3) is the exception and it is deliberate: syncing boards, routing reviews and assigning work are writes only the orchestrator may make (§10.42), and no other skill carries them — so an orchestrator that ends this skill having only described a non-empty queue has stopped halfway.
1. Gather — cheap, no double-reads
CLAUDE.md @-imports HANDOVER.md · LESSONS.md · TASKS.md · rules.md, re-injected from disk after
every compaction — they are ALREADY in context: do not re-Read them wholesale. Exception: if
git status shows one of them MODIFIED (this session's earlier writes, or a parallel co-agent's —
§10.42), re-Read that file: the imported copy predates the edit. Then read only what is NOT auto-loaded:
PLAN.md— the wip phase, its gate, Current focus (skip if the project doesn't use PLAN).git log --oneline -10+git status— what actually landed vs. what is in flight; uncommitted edits are the surest marker of a half-finished item.- Multi-user (
.claude/project-ownerexists): notegit config user.name— the brief scopes to YOUR@tagitems; foreign-owned work is surfaced, never picked up (TASKS ownership). - Agent-team session (the reground hook injected "this session is @"): scope the brief to
that agent's
### <agent>lane and charter paths; re-adopt the identity silently (see/keel-agent-team-start— do not re-run it when the hook already named you).
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.
- today Changed · +31 lines · -79 tokens per session 158422336bc7
- 4d ago First seen · 97 lines · 79 tokens per session scan A e91bbd6e64a0
keel-continue is a skill published in the GitHub repository muratsilahtaroglu/claude-code-starter-kit (9 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,586 tokens. 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
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
sector-rotation
行业轮动分析——申万行业景气度评分、行业动量排名、产业链传导、估值/盈利/资金流多维比较框架.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…