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/jotjunior/cstk/commitnpx skills add JotJunior/cstk --skill commitgit clone --depth 1 https://github.com/JotJunior/cstkWhat 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.00899 |
| Opus 5 | $0.00026 | $0.00449 |
| Sonnet 5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
commit 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 yesterday.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Create a git commit for the current changes following project conventions.
Steps
1. Gather context (run in parallel)
Run these three commands simultaneously:
git status(never use-uallflag)git diff --stagedandgit diffto see all changesgit log --oneline -5to match the repository's commit message style
2. Analyze changes
Review all staged and unstaged changes. Determine:
- Scope: Which services/areas are affected?
- Type: What kind of change? (feat, fix, refactor, docs, chore, test, build)
- Submodules: Are any
services/*submodules modified? If yes, summarize what changed in each.
3. Stage files
- If there are unstaged changes, stage them with
git addspecifying individual files. - NEVER use
git add -Aorgit add .— always add files by name. - NEVER commit files that likely contain secrets:
.env,.env.*,credentials.json, private keys, etc. Warn the user if they exist. - NEVER commit temporary files like
t.txt,*.tmp, scratch files. - If only some changes should be committed, ask the user which files to include.
4. Draft commit message
Follow Conventional Commits format matching the repo's style:
<type>: <short summary in English, imperative mood, under 72 chars>
<optional body: bullet points describing key changes>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Types: feat, fix, refactor, docs, chore, test, build, ci, perf
Rules:
- Summary in English, imperative mood ("add X" not "added X")
- If multiple services changed, list them in the body
- For submodule-only updates, use:
feat: update submodules with <summary> - Always end with
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Examples from this repo:
feat: update submodules with position rules, accent-insensitive collation, and multi-lodge inactive periodsfix: update submodules with proxy header config for real client IPsdocs: atualizar casos de uso
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.
- yesterday First seen · 106 lines · 51 tokens per session scan A 5d55898ef288
commit is a skill published in the GitHub repository JotJunior/cstk (22 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 899 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…