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/klimentij/klimkit/klimkit-setupnpx skills add klimentij/klimkit --skill klimkit-setupgit clone --depth 1 https://github.com/klimentij/klimkitWrote 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/klimentij/klimkit/klimkit-setup)<a href="https://agentmods.dev/skills/klimentij/klimkit/klimkit-setup"><img src="https://agentmods.dev/badge/skills/klimentij/klimkit/klimkit-setup.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.00051 | $0.00874 |
| Opus 5 | $0.00026 | $0.00437 |
| Sonnet 5 | $0.00010 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
klimkit-setup 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 3d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Klimkit Setup
Use this when a repository needs the Klimkit evidence layout and skill routing made explicit. Keep the setup small and reviewable.
Setup Workflow
- Resolve the operator name before creating or migrating files:
- Check the current request and
${XDG_CONFIG_HOME:-~/.config}/klimkit/config.toml. - Check git identity (
git config user.name) as a fallback candidate. - If there is no single clear match, ask the user to choose or provide a name. The
operator name is used for attribution in work
LOG.mdentries.
- Check the current request and
- Ask the user to choose an agent personality, offering two or three options plus a custom name and one-sentence description:
Steady Operator: Direct, careful, evidence-first, and conservative with scope.Product Engineer: Pragmatic, user-facing, and focused on shipping inspectable behavior.Research Scribe: Methodical, source-backed, and explicit about assumptions and decisions.
- Read existing repo instructions:
AGENTS.md,CONTEXT.md,CONTEXT-MAP.md,docs/adr/,README.md, and any existingdocs/work/or legacy.klimkitfiles. - Create the docs-first evidence layout only when meaningful work is starting:
docs/work/README.md— the one-page work-journal convention described in references/artifact-workflow.md.docs/work/.gitignore— ignoring**/.local/.- No separate memory/log/reflection state files: history lives in the
LOG.mdfiles, reflections and decisions are numbered notes in the fitting work phase, and session-binding rules graduate intoAGENTS.md.
- If the repo has a legacy
.klimkit/evidence tree, offer to migrate it intodocs/work/(one work folder per legacy task, authorship recovered intoLOG.mdfiles) instead of leaving two layouts side by side. - Write the selected operator and agent personality to
${XDG_CONFIG_HOME:-~/.config}/klimkit/config.toml. - Add a short repo instruction block only if the repo lacks one. Prefer updating existing
AGENTS.mdover inventing a second instruction file; add aCLAUDE.md → AGENTS.mdsymlink so Claude Code loads the same instructions. The block should cover the work-log rules: journal live, keep phaseLOG.mdupdated, preserve every human message verbatim in exactly one note, never bulk-loaddocs/work/. - Add or update lightweight context docs when useful:
docs/agents/domain.mdfor project language and invariants.
- Recommend relevant Klimkit skills by name in the repo instructions:
klimkit-implement,klimkit-diagnose,klimkit-tdd,klimkit-walkthrough,klimkit-report-server, andklimkit-create-worktree. - Verify that new docs do not expose secrets, machine-local paths, private repo names, or local runtime state.
What ships with it
3 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.
- 3d ago First seen · 44 lines · 51 tokens per session scan A 1f6c37e18cc0
klimkit-setup is a skill published in the GitHub repository klimentij/klimkit (7 stars, last pushed 24d ago), licensed MIT. It adds 51 tokens to every session and 874 once invoked, about $0.0003 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
happiness-skill
当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.
agr-cli
Install, share, sync, and create AI agent skills across coding tools (Claude Code, Cursor, Codex, OpenCode, Copilot, Pi) using the agr CLI. Use whenever the user mentions agr, agr.toml, agr.lock, agrx, or asks to: add a skill ("install the pdf skill", "agr add ..."), sync agent resources across tools, share skills…
agr-release
Release process for the agr package. Handles version bumping (major/minor/patch/beta), changelog updates, pre-release quality checks, git tagging, and monitoring the GitHub Actions publish pipeline. Use this skill whenever the user wants to cut a release, bump the version, publish to PyPI, or asks about the release…
linkedin-post
You take a YouTube video transcript and produce a single LinkedIn post draft.
kafka-dlq-review
Review dead letter queue implementations for completeness using the Lenses MCP server. Checks DLQ topic existence, configuration, monitoring, metadata preservation, retry logic, reprocessing paths and connector DLQ alignment. Use when user says "review dead letter queues", "check DLQ setup", "DLQ audit" or asks about…
kafka-consumer-lag
Analyse Kafka consumer group lag using the Lenses MCP server. Diagnoses lag causes (throughput bottlenecks, rebalancing, partition skew, stalled consumers) and suggests remediation. Use when user says "check consumer lag", "why are consumers slow", "lag report" or asks about consumer group health or offset progress.…