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 viknesh20-20/claude-code-tool-kit --skill write-skillgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/write-skill)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/write-skill"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/write-skill/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/viknesh20-20/claude-code-tool-kit/write-skill"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/write-skill.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.00045 | $0.00753 |
| Opus 5.5 | $0.00018 | $0.00301 |
| Sonnet 5.5 | $0.00009 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
write-skill scanned grade A with 1 finding 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.
Enumerates other installed skillslowAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
!`ls .claude/skills/ 2>/dev/null` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Existing Skills (for pattern reference)
!ls .claude/skills/ 2>/dev/null
Process
Step 1: Gather Requirements
From the user's description, determine:
- Name: lowercase-with-hyphens, becomes the
/slash-command - Purpose: What does this skill do?
- Trigger: When should someone use it?
- Input: What arguments does it need?
- Output: What should it produce?
- Tools needed: Which Claude Code tools does it require?
Step 2: Generate SKILL.md
Create the file following this template:
---
name: skill-name
description: "One sentence: what it does + when to use it. Be specific enough for auto-invocation."
argument-hint: "[argument description]"
allowed-tools: Read, Grep, Glob
---
# Skill Title
## Context Detection
!`relevant shell command for auto-detecting project context`
---
## Instructions
### Step 1: [First action]
Detailed instructions for what Claude should do.
### Step 2: [Second action]
...
### Step N: [Final action]
...
## Output Format
Describe the expected structure of the output.
## Rules
- Rule 1
- Rule 2
Step 3: Validate the Skill
Check the generated SKILL.md against these requirements:
- Frontmatter has
nameanddescription(required) - Description is under 150 characters and specific
-
allowed-toolslists only what's needed (principle of least privilege) - Shell injection uses
!command`` syntax correctly - Instructions are numbered steps, not vague paragraphs
- Output format is defined
- Rules section exists with boundaries
Step 4: Save and Test
- Create directory:
.claude/skills/<skill-name>/ - Save
SKILL.mdto that directory - Instruct user to test: open Claude Code, type
/<skill-name>
Frontmatter Reference
| Field | Required | Description |
|---|---|---|
name |
Yes | Slash command name (lowercase, hyphens) |
description |
Yes | When to use (specific, <150 chars) |
argument-hint |
No | Autocomplete hint, e.g. [filename] |
allowed-tools |
No | Tools allowed without asking |
disable-model-invocation |
No | true = manual only |
user-invocable |
No | false = hidden from menu |
model |
No | Override model |
effort |
No | low, medium, high, max |
context |
No | fork for subagent isolation |
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 · 99 lines · 45 tokens per session scan A 15309e00f45b
write-skill is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 753 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.