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 sebaskauf/skaile-community-library --skill show-and-sharegit clone --depth 1 https://github.com/sebaskauf/skaile-community-libraryWrote 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/sebaskauf/skaile-community-library/show-and-share)<a href="https://agentmods.dev/skills/sebaskauf/skaile-community-library/show-and-share"><img src="https://agentmods.dev/badge/skills/sebaskauf/skaile-community-library/show-and-share/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/sebaskauf/skaile-community-library/show-and-share"><img src="https://agentmods.dev/badge/skills/sebaskauf/skaile-community-library/show-and-share.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.00074 | $0.00665 |
| Opus 5 | $0.00037 | $0.00332 |
| Sonnet 5 | $0.00015 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
show-and-share 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 12d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show & Share Post
Du schreibst einen kurzen, fertigen Vorstellungs-Post für die Skool-Kategorie "Show & Share" der SKAILE Community. Der User hat einen Skill, ein Plugin oder eine Vorlage gebaut und will sie der Community zeigen.
Schritt 1: Verstehen, was gebaut wurde
Lies die Quelle, statt zu raten:
- Skill/Plugin: Lies die SKILL.md (und plugin.json). Daraus ergibt sich, was es macht und wann es triggert.
- Vorlage/Datei (CLAUDE.md, Prompt, settings): Lies die Datei und den Kommentar-Block oben.
- Wenn der User nur erzählt, was er gebaut hat: kurz nachfragen, falls der Mehrwert unklar ist. Maximal eine Rückfrage.
Schritt 2: Post schreiben
Halte dich exakt an dieses Format (das ist die Community-Konvention):
🛠️ Mein Skill: [name]
Was macht er: [2-3 Sätze. Erst das Problem, dann die Lösung. Konkret, nicht abstrakt.]
So nutzt du ihn: [Der Satz oder Prompt, den man Claude sagt. In Anführungszeichen.]
Installieren: /plugin install [name]@skaile-community-library
[Optional: 1 Satz, was als Nächstes geplant ist oder wofür Feedback gewünscht ist]
Feedback und Ideen gerne hier drunter 👇
Für Vorlagen (kein installierbares Plugin) ersetze die Installieren-Zeile durch:
Du findest sie in der Library unter resources/: https://github.com/sebaskauf/skaile-community-library
Wenn der Skill noch im Review ist (PR offen, noch nicht gemergt), schreibe statt der Installieren-Zeile: Ist gerade im Review, sobald freigeschaltet: /plugin install [name]@skaile-community-library
Stil-Regeln
- Kurz: maximal ~120 Wörter. Niemand liest Textwände im Feed.
- Mehrwert vor Technik: "Spart dir 10 Minuten pro README" schlägt "nutzt Frontmatter-Parsing".
- Ehrlich: nichts versprechen, was der Skill nicht kann. Kein Marketing-Sprech, kein "revolutionär".
- Du-Form, locker, 1-2 Emojis maximal.
- Deutsch, Tech-Begriffe auf Englisch lassen, echte Umlaute (ä/ö/ü/ß).
Schritt 3: Übergeben
Gib den fertigen Post als reinen Text aus, damit der User ihn direkt kopieren und in Skool posten kann. Auf macOS biete an, ihn in die Zwischenablage zu legen (LC_CTYPE=UTF-8 pbcopy, sonst gehen Umlaute kaputt).
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.
- 12d ago First seen · 54 lines · 74 tokens per session scan A 039e71f87c06
show-and-share is a skill published in the GitHub repository sebaskauf/skaile-community-library (6 stars, last pushed 12d ago), licensed MIT. It adds 74 tokens to every session and 665 once invoked, about $0.0004 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
exec
A procedure for running programs that may take more than a few dozen seconds, such as training jobs, evaluations, data processing, or servers, while recording logs and detecting failures.
survey
A project-discovery workflow that creates `.claude/context.md`, a shared file describing the project's purpose, design, constraints, and measures of success.
release
A release guide for publishing a software package, including projects with multiple independently versioned packages in one repository, called a monorepo. It determines the release unit, updates versions using Semantic Versioning, and prepares the related GitHub release steps after approval.
commit
A Git workflow for dividing uncommitted changes into meaningful commits and proposing complete commit messages before recording them.
complete
A skill for completing university assignments that contain several kinds of work, such as a report and a program. It divides the requirements between the appropriate skills and checks that the finished pieces agree with each other.
skill
A general repair skill for when an add-on gives a wrong result, misses something, or receives negative feedback. It finds the rule or instruction that caused the problem and updates it.