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/validation)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/validation"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/validation/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/validation"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/validation.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.00023 | $0.00576 |
| Opus 5.5 | $0.00009 | $0.00230 |
| Sonnet 5.5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
validation 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 18d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation
Invocation: kc-dev-flow-2:validation
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.
Read the framework for authority and stage ownership. Required inputs: the exact work item, recorded variant/profile, current stage, approved scope and the stage's available artifact/evidence. Resolve inconsistencies with FO rather than inferring a selection or loading another variant.
Profile routes
| Profile | Availability | Profile principles | Stage reference |
|---|---|---|---|
| poc | active | poc | poc |
| pilot | active | pilot | pilot |
| prod | active | prod | prod |
Select the recorded row and read its shared profile principles first, then
stage principles, then that row's stage reference and relevant
adopted project learning. A skip row means report the inapplicable dispatch;
do not perform stage work or create an extra gate. Unknown profiles or missing
references require a hold report, not a default route.
Before useful work, a resumed or reused worker re-establishes these inputs and
loads the current selected references. End the dispatch context with a short
profile/boundary reminder rather than another copy of the rules.
When work changes retained documents or behavior they describe, read
retained-document practices.
Return the stage output and unresolved decisions to FO in a stage report
Spacedock 0.27.2 parses by exact form: a ## Stage Report: <stage> heading with
nothing else on that line, then unindented - DONE: <item>, - SKIPPED: <item>,
or - FAILED: <item> bullets — not - [x]. Checklist parsing stops at the first
### sub-heading, so put any ### sections after the bullets, not inside them.
FAILED: marks only an item that was not met; a report with nothing failed has
no FAILED: bullet, and a summary such as "FAILED: none" is never a bullet.
This skill grants no state, approval or delivery authority.
What ships with it
4 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.
- 18d ago Changed · +6 lines 50b745fa305e
- 27d ago Changed · +4 lines 1aa339f21260
- 1mo ago First seen · 37 lines · 23 tokens per session scan A 4f5df1718a7d
validation is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 576 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-09-16.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.