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/statusnpx skills add fullymiddleaged/Clawness --skill statusgit 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.00039 | $0.00616 |
| Opus 5 | $0.00019 | $0.00308 |
| Sonnet 5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
status 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clawness Status
Show the user what's currently active in their Clawness setup.
Running the Clawness CLI. It ships with the plugin but isn't on your PATH. Use the wrapper the SessionStart bootstrap hook writes each session:
CLAW="${CLAUDE_CONFIG_DIR:-$HOME/.claude}/clawness/clawness-cli.sh" bash "$CLAW" <command> # e.g. bash "$CLAW" statsIf
$CLAWdoesn't exist, the bootstrap hasn't run yet — start a fresh session. (Editable/manual installs may instead usepython -m clawness.cli ....)
Keep this FAST — it's a quick health check, not a full scan. Step 1 already proves retrieval at zero cost, so a test query is unnecessary.
Steps
-
Report the rules you already see (no command). You (Claude) receive the Clawness rule block at the top of your context this turn. Summarize it: how many mandatory + relevant rules, and a few rule IDs. If you see it, injection is working — this alone is the health check.
If you do NOT see an injected block, say so plainly and do not rationalize it. The hook injects the global rules on every prompt in every directory — the working directory (including being in the Clawness source repo) does not disable injection; it only affects the optional
.clawness/rules/project overlay. A missing block means the hook is not running — either not loaded this session (needs a restart //reload-plugins) or erroring (check/hooksandclaude --debug). Never attribute a missing block to the current directory. -
Show the corpus + token cost. Run (fast):
bash "$CLAW" statsReport total rules, domains, and the
Tokens / turnline. -
Project rules (only if present). If
.clawness/rules/exists in the project (walk up to the git root), mention it; otherwise skip silently.
Summary — keep it to a few lines:
- Rule injection: working (you saw the block) / not seeing rules
- Global rules: N across M domains; ~N tokens/turn (tune with
CLAW_TOP_K,CLAW_VERBOSE,CLAW_COMPACT) - Project rules: N, or "none —
bash \"$CLAW\" init .to add some"
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 · 54 lines · 39 tokens per session scan A ddb37437f2ea
status is a skill published in the GitHub repository fullymiddleaged/Clawness (3 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 616 once invoked, about $0.0002 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, что умеет стек, как запускать.