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/refreshnpx skills add fullymiddleaged/Clawness --skill refreshgit 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.00088 | $0.02005 |
| Opus 5 | $0.00044 | $0.01002 |
| Sonnet 5 | $0.00018 | $0.00401 |
| Haiku 4.5 | $0.00009 | $0.00200 |
Grade A, and why
refresh 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refresh rules for a framework version
Clawness rules can carry a version stamp — applies_to, verified, sources —
recording the range they were established against. When a project runs past that
range, 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 destructive work. You invoking this skill is the consent it couldn't ask for.
This is the only path permitted to author rule files. Nothing automatic may invoke it — not the note, not a hook, not your own initiative mid-task. An earlier version of this 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:refresh <domain> — one domain (nextjs, react, python, fastapi,
…). With no argument, use the detected stack, and if that spans several domains ask
which one. One domain per run. Reviewing several at once is how a careful pass
becomes a bulk stamp, which is the failure this whole feature exists to prevent.
Steps
1. Establish what is actually installed
The lockfile is authoritative; the manifest range is not. ^17.0.0 in
package.json is a permission, not a fact — read package-lock.json,
pnpm-lock.yaml, yarn.lock, uv.lock, poetry.lock, or pip freeze output for
the resolved version. This is GEN-INSTALLED-VER-001's procedure, and it matters
more here than usual: the rule you write will be asserted to future sessions as
fact.
If you cannot resolve an exact version, say so and stop. Do not write a rule against a version you had to guess.
2. Establish what the codebase actually uses
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 · 175 lines · 88 tokens per session scan A 96f93765f775
refresh is a skill published in the GitHub repository fullymiddleaged/Clawness (3 stars, last pushed 3d ago), licensed MIT. It adds 88 tokens to every session and 2,005 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
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.
performance
CLI performance optimization - startup time, memory usage, token savings benchmarking.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
orchestrator-lanes
Claude Code dev-orchestrator only. File-based multi-lane PM playbook (score, DAG, run-controller, L0/L1/L2, ship). Use when this session IS that agent, or user says info / справка / lane-stack:orchestrator-lanes info. SKIP: Grok, Codex, Kimi, Qwen, AGY, Cursor writer CLIs and any default coding agent — do not load, do…
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
info
Lane-stack work-process cheat sheet. Catalog of resume, onboard, architect a new app, design, docs. Use when user says info, справка, lane-stack:info, /lane-stack:info, что умеет стек, как запускать.