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/ssube/conclave/skill-creatornpx skills add ssube/conclave --skill skill-creatorgit clone --depth 1 https://github.com/ssube/conclaveWhat 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.00057 | $0.01846 |
| Opus 5 | $0.00028 | $0.00923 |
| Sonnet 5 | $0.00011 | $0.00369 |
| Haiku 4.5 | $0.00006 | $0.00185 |
Grade A, and why
skill-creator 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 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.
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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Guide for creating effective skills. Merged from the Agent Skills specification and the aivena skill-creator by Espen Nilsen.
Quick Reference
# Scaffold a new skill
python3 {baseDir}/scripts/init_skill.py <skill-name> --path <target-directory>
# Example: create a new skill in your skills directory
python3 {baseDir}/scripts/init_skill.py my-new-skill --path ./skills
Core Principles
1. Context Is a Public Good
The context window is shared with the system prompt, conversation history, other skills, and the user's request. Default assumption: Claude is already very smart. Only add context Claude doesn't already have.
Challenge each piece: "Does Claude really need this?" and "Does this justify its token cost?"
Prefer concise examples over verbose explanations.
2. Progressive Disclosure
Skills use three-level loading:
- Metadata (name + description) — Always in context. ~100 words. This is the trigger.
- SKILL.md body — Loaded on-demand when the skill triggers. Keep under 500 lines.
- Bundled resources — Loaded only when specifically needed. Unlimited size.
If SKILL.md approaches 500 lines, split content into references/ files and link to them.
3. Degrees of Freedom
Match specificity to fragility:
- High freedom (text instructions): Multiple approaches valid, context-dependent decisions
- Medium freedom (pseudocode/scripts with parameters): Preferred pattern exists, some variation OK
- Low freedom (exact scripts, few parameters): Operations fragile, consistency critical
A narrow bridge needs guardrails. An open field allows many routes.
Skill Structure
skill-name/
├── SKILL.md # Required: frontmatter + instructions
├── scripts/ # Executable code (Python/Bash)
│ └── process.sh
├── references/ # Detailed docs loaded on-demand
│ └── api-reference.md
└── assets/ # Files used in output (templates, images)
└── template.json
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 257 lines · 57 tokens per session scan A 4a01594b7106
skill-creator is a skill published in the GitHub repository ssube/conclave (2 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 1,846 once invoked, about $0.0003 per session on Opus 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-31.
Other skills, from other repositories
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
system-prompts
Write system prompts, tool docs, and agent definitions. Project tag conventions + RFC 2119 keywords + dense compression. Use when authoring or editing any prompt the model reads.
tool-prompt-optimization
Optimize the description prompts an AI agent reads to learn its built-in tools (the .md files under prompts/tools/). Two halves: (1) measure how much of a prompt is already inferable from the tool's JSON parameter schema + name, to prune redundancy with evidence; (2) house authoring rules for what belongs in a tool…
archon-cli
Drive Archon through its CLI: run AI workflows on a repo, manage those runs (inspect, approve, reject, cancel, resume), set up Archon or change its config, author new workflows, and improve workflow prompts. Use when the user says "use archon", "run archon", "archon workflow", "fix issue #N with archon", "have archon…
semantic-compression
Re-encode verbose prose into a dense telegraphic register — punctuation as connectives, label frames, verbless assertions — without losing normativity or precision. Use when compressing system prompts, tool/function descriptions, skill bodies, or agent instructions; reducing token count or context bloat; making…
coding-agent-standards
Defines practical standards for implementation-focused coding agents. Use when creating or editing code, especially when reliability, clarity, and low-risk delivery are required.