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/bugrabilge/bilge-development-kit/create-skillnpx skills add bugrabilge/bilge-development-kit --skill create-skillgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWhat 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.00046 | $0.00943 |
| Opus 5 | $0.00023 | $0.00472 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
create-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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
/create-skill api-test automated API endpoint testing with curl How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-skill - Skill Generator
$ARGUMENTS
Purpose
Generate a new Claude Code skill (slash command) from a natural language description. Creates properly structured SKILL.md with frontmatter, behavior rules, and output format.
Behavior
When /create-skill is triggered:
Step 1: Parse Input
Extract from user's description:
- Skill name: lowercase, hyphenated (e.g.,
api-test,changelog) - Purpose: what the skill does
- Trigger terms: when should it activate
If input is vague, ask:
- What should this skill do?
- Does it modify code or only analyze/report?
- What sub-commands should it have?
Step 2: Determine Skill Type
| Type | Characteristics | disable-model-invocation |
|---|---|---|
| Analysis | Read-only, generates reports | true |
| Generator | Creates new files/code | true |
| Interactive | Asks questions, explores options | false |
| Automation | Runs scripts, orchestrates agents | true |
Step 3: Generate SKILL.md
Create .claude/skills/{name}/SKILL.md with this structure:
---
name: {skill-name}
description: >
{One-line purpose}.
Use when: {comma-separated trigger terms}
argument-hint: "{expected arguments}"
user-invocable: true
disable-model-invocation: {true|false}
---
# /{skill-name} - {Title}
$ARGUMENTS
---
## Purpose
{What this skill does and why it exists.}
---
## Sub-commands
{If applicable}
---
## Behavior
When `/{skill-name}` is triggered:
### 1. {First Step}
{Description}
### 2. {Second Step}
{Description}
### 3. {Third Step}
{Description}
---
## Output Format
{Expected output template}
---
## Examples
{Usage examples}
---
## Key Principles
- {Principle 1}
- {Principle 2}
- {Principle 3}
Step 4: Validate
Check generated skill:
- Name is lowercase, hyphenated, max 30 chars
- Description fits in 250 chars (budget limit)
- Has clear trigger terms in description
-
$ARGUMENTSplaceholder is present - No unsupported frontmatter fields
- Output format is defined
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.
- 2d ago First seen · 174 lines · 46 tokens per session scan A 1086c04ef4c1
create-skill is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 943 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
geo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…