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 barockok/slaude --skill skill-authoringgit clone --depth 1 https://github.com/barockok/slaudeWrote 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/barockok/slaude/skill-authoring)<a href="https://agentmods.dev/skills/barockok/slaude/skill-authoring"><img src="https://agentmods.dev/badge/skills/barockok/slaude/skill-authoring/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/barockok/slaude/skill-authoring"><img src="https://agentmods.dev/badge/skills/barockok/slaude/skill-authoring.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.00015 | $0.00446 |
| Opus 5.5 | $0.00006 | $0.00178 |
| Sonnet 5.5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
skill-authoring 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 today.
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.
What it actually says
Skill evolution (grow over time)
- You can author your own skills. Each skill is a markdown file at
~/.slaude/skills/<slug>/SKILL.mdinvoked later as/<slug>. Themcp__slaude_skills__*server exposes:list_skills,read_skill,write_skill,delete_skill,sync_manifest— all usable freely, no approval card needed. Skills are agent-owned and reversible. - At the end of a turn that took several steps and showed a procedure
you would plausibly repeat, evaluate before your final reply:
- Call
list_skillsif you don't already know what exists. - Did this turn demonstrate a repeatable procedure not yet captured
in a skill? →
write_skill(new slug, clear description, parameterised body using${SLAUDE_SKILL_ARGS}). - Did this turn refine or contradict an existing skill? →
read_skill, thenwrite_skillto overwrite with the improved version. Preserve prior intent; don't silently truncate. - Neither? → do nothing. Skill bloat is worse than skill absence.
- Call
- Do not announce a skill save or update unless the user asked for the skill. Never narrate routine auto-evolve evaluations.
- Skills are for procedures (steps, checklists, tool sequences), not for one-off facts (those belong in memory). If the lesson is "remember X", write it to memory instead.
- Keep skill bodies short and operational. Reference inputs via
${SLAUDE_SKILL_ARGS}, the working dir via${SLAUDE_SKILL_DIR}, the session id via${SLAUDE_SESSION_ID}.
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.
- today First seen · 32 lines · 15 tokens per session scan A 1113eb48ca6e
skill-authoring is a skill published in the GitHub repository barockok/slaude (6 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 446 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-10-26.
Other skills, from other repositories
agent-goal-skill
Take a rough goal description and shape it into a polished, doctrine-compliant agent goal prompt. Output is for the user to copy/paste into Codex, Claude Code (native /goal), Droid, Auggie, or any CLI agent that benefits from a structured goal contract. The skill does NOT execute the goal — it shapes the prompt and…
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.