Borrowing it
Nothing to install: this file belongs to Tatsh/wiswa-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Tatsh/wiswa-mcp/master/.claude/skills/ci/SKILL.mdgit clone --depth 1 https://github.com/Tatsh/wiswa-mcpWrote 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/tatsh/wiswa-mcp/ci)<a href="https://agentmods.dev/skills/tatsh/wiswa-mcp/ci"><img src="https://agentmods.dev/badge/skills/tatsh/wiswa-mcp/ci/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/tatsh/wiswa-mcp/ci"><img src="https://agentmods.dev/badge/skills/tatsh/wiswa-mcp/ci.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.00000 | $0.02001 |
| Opus 5 | $0.00000 | $0.01001 |
| Sonnet 5 | $0.00000 | $0.00400 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
ci 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 9d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Create high-quality Git commits for all pending changes.
Gathering context
Run these in parallel:
git diff- unstaged changes.git diff --cached- staged changes.git status- untracked files and overall state.git log --no-merges --format='%s%n%b---' -20 | grep -v '^bump:' | grep -iv dependabot- recent commit message style examples.
Running agents
After gathering context but before committing, determine which agents to run based on the changed
files. Launch each agent sequentially using the Agent tool with subagent_type general-purpose,
telling it to follow the corresponding .claude/agents/<name>.md file. Scope each agent to only the
changed files, not the entire project.
You must skip any agents that are not relevant to the changed files (e.g. if no Click command files changed, skip the click-auditor).
When Python code is being committed
If any changed files are under wiswa/mcp/ or tests/, run the following
agents in order:
- python-moderniser - upgrade to modern Python features.
- click-auditor - validate Click command consistency. Only run if files under
wiswa/mcp/commands/changed. - docstring-fixer - fix missing or incomplete docstrings.
- copy-editor - fix prose in comments, docstrings, and strings.
- test-writer - generate/update tests for new/changed code. Skip if the only changes are in
tests/. - qa-fixer - format and fix lint/spelling issues.
When user-facing changes are being committed
-
changelog - update
CHANGELOG.mdonly for user-facing changes (behaviour, CLI, public API, security, or meaningful dependency constraints that affect installs). After it completes, check ifCHANGELOG.mdwas modified (git diff CHANGELOG.md). If it was, stage it with the relevant commit. Follow.claude/agents/changelog.md, including its skip list.Files under
wiswa/mcp/,tests/, or version changes inpyproject.tomlare candidates for the changelog agent only when they change what users see or how the software behaves. Editing those paths is not sufficient on its own.
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.
- 9d ago First seen · 182 lines · 0 tokens per session scan A 5d1a505edd1d
ci is a skill published in the GitHub repository Tatsh/wiswa-mcp (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,001 tokens. 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
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.
conventional-commits
Write clear, conventional git commit messages — type(scope): summary, imperative mood, a body that explains the why.
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…
session-cleanup
Verify debug/dev artifacts are removed before commit. Use at session end to apply 'good boy scout' rule - leave code cleaner than you found it.
speckit-git-commit
Auto-commit changes after a Spec Kit command completes.
speckit-git-initialize
Initialize a Git repository with an initial commit.