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.
git clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/commands/saajunaid/caddis-plugin/create-skill)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/create-skill"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/create-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/commands/saajunaid/caddis-plugin/create-skill"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/create-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.00017 | $0.00816 |
| Opus 5.5 | $0.00007 | $0.00326 |
| Sonnet 5.5 | $0.00003 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
create-skill 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-skill - Create a New Skill
Create or generate a SKILL.md file that teaches the AI agent specialized knowledge, workflows, or tool integrations.
Input
User's request: {{input}}
If {{input}} is empty, ask: "What capability should this skill add? Or should I analyze the repo to discover patterns?"
Option A: Create from Description
When the user describes what the skill should do:
- Clarify the skill's purpose, triggers, and target workflows
- Read the skill creator guide at
skills/workflow/skill-creator/SKILL.mdfor format and best practices - Create the skill following the structure below
Option B: Generate from Repository Analysis
When the user wants to extract patterns from the codebase:
Step 1: Gather Data
# Recent commits with file changes
git log --oneline -n 200 --name-only --pretty=format:"%H|%s|%ad" --date=short
# Most frequently changed files
git log --oneline -n 200 --name-only | sort | uniq -c | sort -rn | head -20
# Commit message patterns
git log --oneline -n 200 | head -50
Step 2: Detect Patterns
| Pattern Type | What to Look For |
|---|---|
| Commit conventions | Consistent prefixes (feat:, fix:, chore:) |
| File co-changes | Files that always change together |
| Workflow sequences | Repeated multi-file change patterns |
| Architecture | Folder structure and naming conventions |
| Testing patterns | Test locations, naming, framework |
Step 3: Generate SKILL.md
Create the skill from detected patterns.
Skill Structure
skills/{category}/{skill-name}/
├── SKILL.md (required)
├── scripts/ (optional - executable code)
├── references/ (optional - docs the agent reads)
└── templates/ (optional - starter files)
SKILL.md Format
---
name: {skill-name}
description: "{What it does}. Use when {triggers/scenarios}."
category: {coding|testing|workflow|docs}
---
# {Skill Name}
{Brief overview of what this skill provides.}
## When to Use
- {Trigger scenario 1}
- {Trigger scenario 2}
## Prerequisites
- {Required tools or setup}
## Workflows
### {Workflow 1 Name}
1. {Step 1}
2. {Step 2}
3. {Step 3}
## Guidelines
- {Guideline 1}
- {Guideline 2}
## Troubleshooting
| Issue | Solution |
|-------|----------|
| {Problem} | {Fix} |
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 · 136 lines · 17 tokens per session scan A e448c9cc182e
create-skill is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 816 once invoked, about $0.0001 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-09-09.
Other commands, from other repositories
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
accept
Command dispatcher for accept.
change
Command dispatcher for change.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.