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 JotJunior/cstk --skill commitgit clone --depth 1 https://github.com/JotJunior/cstkWrote 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/jotjunior/cstk/commit)<a href="https://agentmods.dev/skills/jotjunior/cstk/commit"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/commit/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/jotjunior/cstk/commit"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 40 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00051 | $0.00899 |
| Opus 5.5 | $0.00020 | $0.00360 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 106 lines · 51 tokens per session scan A 5d55898ef288
commit is a skill published in the GitHub repository JotJunior/cstk (24 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 899 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-08-30.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
git-pr-strategy
Apply safe branching, commits, conflict resolution, review ownership, merge, rollback, and release-tag rules.
cc-autopilot
Run cc-autopilot, a perpetual autonomous AUDIT/GENERATE→TRIAGE→BATCH→FIX→VERIFY→REVIEW→COMMIT loop that holds every change to a configured quality bar through a judge panel. Its fixers each own a file-disjoint slice of the tree so no two can ever touch the same file, and nothing unverified reaches git. Works on a web…
git-workflow
Branch naming, commit message format, and PR conventions. Use when making git commits or creating PRs.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.