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 iamcxa/kc-claude-plugins --skill continue-dev-flowgit clone --depth 1 https://github.com/iamcxa/kc-claude-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/iamcxa/kc-claude-plugins/continue-dev-flow)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/continue-dev-flow"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/continue-dev-flow/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/iamcxa/kc-claude-plugins/continue-dev-flow"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/continue-dev-flow.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.00034 | $0.02549 |
| Opus 5.5 | $0.00014 | $0.01020 |
| Sonnet 5.5 | $0.00007 | $0.00510 |
| Haiku 4.5 | $0.00003 | $0.00255 |
Grade A, and why
continue-dev-flow 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue Dev Flow
Continue by the selected profile's smallest sufficient route.
Resolve authority before policy
- Locate the workflow README via the nearest repository instructions. Require
the unique ordered
kc-dev-flow-static-local-profilestart/end marker pair, with## Local Profileimmediately after start. Read only its frontmatter and marked block; never infer boundaries from headings or open the full README. - Resolve repository root; recheck worktree, branch, shared-state owner and delivery state.
For reviewable delivery, list open artifacts before branch creation/reuse.
Stack on an unmerged dependency's source branch without waiting for merge.
delivery-branch-base.mdowns this default and exceptions across ceremonies. - Read the exact committed work item and selected brief. A Pilot or
Production new admission requires one Development Brief containing the
problem, accepted outcome, complete non-goal list, route-back conditions, and
one canonical
## Acceptance criteriasection with unique ascendingAC-Nbullets. A POC item uses its complete v3 decision, falsifier, budget, and stop condition as the Exploration Brief. Do not read current execution state or revalidate and rewrite an already-admitted item's historical headings. A Pilot or Production item's new admission is the dispatch whose targetworkflow_stageis that profile's first route stage (ideation) with no prior stage pin recorded for this item; that dispatch's loader invocation (below) adds--validate-admissionand stops on a non-zero exit, quoting the exactprofile contract: ...stderr line to the Captain rather than dispatching. A subsequent stage's dispatch for the same already-admitted item omits the flag. - Before dispatch and whenever execution proposes a scope change, compare the
accepted goal and complete non-goal list exactly with the admission snapshot.
If either differs or must change, stop; do not replace the snapshot or
candidate. Return a structured planning delta naming the changed premise,
affected acceptance evidence, and recommended
changeorstop. - Then read current execution state from its declared authority. Do not enumerate the state tree or use provider status to advance execution.
- Re-read
## Work profile receipt. New choices use v3; compatible v2 Pilot and Production receipts remain loadable, while an active v2 POC must finish on its pinned 3.x pair or be Captain re-recorded. If the receipt is missing or stale before the first working stage, invokekc-dev-flow:choose-work-profile; let the locally authorized actor commit and re-read the Captain's choice. An unchanged v1 Pilot or Production choice upgrades mechanically. For a v1 POC, preserve the choice but usekc-dev-flow:choose-work-profileto complete the v3 POC fields with the Captain before dispatch.
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.
- 1mo ago Changed · +28 lines bcea00ee6484
- 1mo ago Changed · -78 lines 8f74a3dba03e
- 1mo ago Changed · -7 lines eae7f6e46d1f
- 1mo ago Changed · +6 lines 5db194ead89a
- 1mo ago Changed · +2 lines 4d26a633b983
- 1mo ago First seen · 259 lines · 34 tokens per session scan A ca39b3c11899
continue-dev-flow is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 2,549 once invoked, about $0.0001 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…
implement-issue
Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.