Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add iamcxa/kc-claude-plugins/plugin install kc-dev-flow-2Wrote 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/learn)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/learn"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/learn/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/learn"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/learn.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.00044 | $0.04544 |
| Opus 5.5 | $0.00018 | $0.01818 |
| Sonnet 5.5 | $0.00009 | $0.00909 |
| Haiku 4.5 | $0.00004 | $0.00454 |
Grade A, and why
learn 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 4d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learn
Invocation: kc-dev-flow-2:learn
Package root: ${CLAUDE_PLUGIN_ROOT}
<package> in this skill and its linked files is this root. If the value above
is not an absolute path, the root is two directories above this SKILL.md.
Run under the existing First Officer (FO) orchestration. This is an explicit
named-task operation, run by hand or by FO at archive when the repository lists the
learn extension; it is not a scanner, new SD
stage, hook or background launcher.
Read the framework and preserve project/Captain authority.
Resolve the absolute code root and workflow directory, exact archived task slug,
activated SD executable and package, and original code repository. Retain
--workflow-dir throughout. Missing/contradictory evidence holds this learning
operation without reopening or mutating the closed development task.
Bind closure and the original delivery
Use the existing SD read interfaces (pass resolved values as data):
${SPACEDOCK_BIN:-spacedock} status --workflow-dir "$FLOW" --boot --identify --json
${SPACEDOCK_BIN:-spacedock} status --workflow-dir "$FLOW" --resolve "archive:slug:$SLUG" --json
${SPACEDOCK_BIN:-spacedock} status --workflow-dir "$FLOW" --read "archive:slug:$SLUG" --json
Require the expected definition directory, present entity checkout, resolve scope
archived and matching exact slug/path. Read frontmatter must have a terminal
status from the actual boot taxonomy, verdict: passed, nonempty completed,
empty mod-block, variant: kc-dev-flow-2 and a valid selected profile. SD booleans
may be strings. --archived includes active tasks; do not use an archived=true
frontmatter filter to infer closure.
Resolve the state Git root and archive-relative path. Require clean task bytes,
then inspect git log -1 --diff-filter=A --no-renames --format=%H -- ARCHIVE_REL
and git show CLOSURE_COMMIT:ARCHIVE_REL from that root. The commit must introduce
the current terminal/passed archive, with current bytes matching its snapshot;
state HEAD, an archive filename or commit subject alone is insufficient. Missing
history, later unaccounted edits or an ambiguous imported archive require a hold.
Bind companion evidence to immutable state paths/revisions too.
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.
- 4d ago Changed · +94 lines 428063102810
- 5d ago Changed · +2 lines · +9 tokens per session 64cb87cbb400
- 8d ago Changed · +7 lines 2a3877f73794
- 18d ago Changed · +4 lines 0b0c30807e09
- 24d ago Changed · +11 lines c3daa45855ae
- 27d ago Changed · +9 lines d2d464cc903b
- 1mo ago Changed · +17 lines 25c0313c127e
- 1mo ago First seen · 166 lines · 35 tokens per session scan A a902508a36e3
learn is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 4,544 once invoked, about $0.0002 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-09-17.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.