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/fullymiddleaged/clawness/bootstrapnpx skills add fullymiddleaged/Clawness --skill bootstrapgit clone --depth 1 https://github.com/fullymiddleaged/ClawnessWhat 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.00110 | $0.01617 |
| Opus 5 | $0.00055 | $0.00809 |
| Sonnet 5 | $0.00022 | $0.00323 |
| Haiku 4.5 | $0.00011 | $0.00162 |
Grade A, and why
bootstrap 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap rules for an uncovered stack
Clawness ships corpus for ~29 domains. Open a session in a stack it has no rules for and, beyond the always-on mandatory block, it adds little. A SessionStart note says so once and deliberately does nothing else.
This skill is the remedy. The note is only the diagnosis: it fires before you have said what you came for, so it cannot propose a session's worth of work. You invoking this skill is the consent it couldn't ask for.
This is a rule-authoring path, so the same discipline as /clawness:refresh
applies. Nothing automatic may invoke it — not the note, not a hook, not your own
initiative mid-task. An earlier version of a related feature let the automatic path
write rules and it produced heaps of them, consuming a session opened for something
else.
Say this before starting. It takes a while, it writes files into the project, and the rules it writes will govern every future prompt in this repo. Get an explicit go-ahead, and tell them nothing is written until they approve the list.
Argument
/clawness:bootstrap [stack] — the ecosystem to write rules for (ruby, elixir,
haskell, …). With no argument, use the uncovered stack the note named; if the
repo mixes several uncovered stacks, ask which one. One stack per run — a broad
pass over several is how a careful review becomes a batch of slop.
Steps
1. Establish what the project actually is
Read enough of the codebase to know the stack, its version, and its shape — the web framework or libraries in use, the build tool, the conventions the existing code already follows. Rules must fit THIS project, not the language in the abstract. A rule the codebase already obeys is noise; a rule that contradicts the house style is worse.
2. Look up current conventions — from documentation, not memory
For each candidate rule, ground it in a current official source: the language
or framework's own docs, style guide, or security guidance. Record the URL you
used — it becomes the rule's sources and is what makes the rule auditable rather
than asserted.
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 · 135 lines · 110 tokens per session scan A 74aac498974f
bootstrap is a skill published in the GitHub repository fullymiddleaged/Clawness (3 stars, last pushed 4d ago), licensed MIT. It adds 110 tokens to every session and 1,617 once invoked, about $0.0006 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
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
pr-review
Batch review des PRs RTK par ordre de complexité croissante (XS → S → M → L). Pour chaque PR : vérifie l'état (conflits, CLA, reviews), lit le diff complet, analyse le code en contexte, présente un résumé avec lien + taille + recommandation. Attend validation explicite avant tout merge. Poste des commentaires…
rtk-triage
Triage complet RTK : exécute issue-triage + pr-triage en parallèle, puis croise les données pour détecter doubles couvertures, trous sécurité, P0 sans PR, et conflits internes. Sauvegarde dans claudedocs/RTK-YYYY-MM-DD.md. Args: "en"/"fr" pour la langue (défaut: fr), "save" pour forcer la sauvegarde.
code-simplifier
Review RTK Rust code for idiomatic simplification. Detects over-engineering, unnecessary allocations, verbose patterns. Applies Rust idioms without changing behavior.
performance
CLI performance optimization - startup time, memory usage, token savings benchmarking.