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/openclaw-auditnpx skills add fullymiddleaged/Clawness --skill openclaw-auditgit clone --depth 1 https://github.com/fullymiddleaged/ClawnessWrote 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/fullymiddleaged/clawness/openclaw-audit)<a href="https://agentmods.dev/skills/fullymiddleaged/clawness/openclaw-audit"><img src="https://agentmods.dev/badge/skills/fullymiddleaged/clawness/openclaw-audit.svg" alt="Measured on agentmods" 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 | $0.00121 | $0.02557 |
| Opus 5 | $0.00060 | $0.01278 |
| Sonnet 5 | $0.00024 | $0.00511 |
| Haiku 4.5 | $0.00012 | $0.00256 |
Grade A, and why
openclaw-audit 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 5d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trim an OpenClaw workspace prompt
OpenClaw assembles its system prompt fresh for every agent turn. Alongside the fixed
sections it manages (Tooling, Safety, Skills, Workspace, …), it injects the workspace's
own Markdown files in full, every turn: AGENTS.md, SOUL.md, IDENTITY.md,
USER.md, BOOTSTRAP.md (new workspaces only, self-deletes after first run), and
MEMORY.md when present. That injected block is the one part of the per-turn cost the
workspace owner controls — and the usual "landslide of noise per turn" complaint is it
growing unchecked. OpenClaw caps it at 20,000 chars per file and 60,000 total and
truncates past that with a terse notice, which is a worse outcome than trimming on
purpose: you don't choose what gets cut.
This skill is the remedy, the OpenClaw sibling of /clawness:claude-md. It is opt-in
work: you invoking it is the consent, because a good trim is destructive and takes a while.
Say this before starting. This reorganises files the user may care about a great deal (SOUL.md is the agent's personality), and it takes most of a session. Tell them: nothing is deleted until its replacement is verified, and they can stop after any single file. Then get an explicit go-ahead.
Filenames and limits below are from OpenClaw's public docs, not a live install. Before you measure, confirm the workspace path and the file set actually present — see the same caution in openclaw/README.md ("Assumptions to verify"). The default workspace is
~/.openclaw/workspace/; the user may point elsewhere.
First: is this the right tool?
This skill earns its place only when Clawness is running under OpenClaw (the openclaw/
TypeScript adapter shelling out to the Python hooks), because the whole point is to move
bulk out of always-injected files and into Clawness's ranked retrieval, which the
adapter provides via the before_prompt_build hook. Without that adapter installed there
is nowhere cheaper for the content to go, and you should stop and say so — trimming a
workspace file with no ranked destination just loses information.
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.
- 5d ago First seen · 170 lines · 121 tokens per session scan A 2e1383aab2f7
openclaw-audit is a skill published in the GitHub repository fullymiddleaged/Clawness (3 stars, last pushed 7d ago), licensed MIT. It adds 121 tokens to every session and 2,557 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
moai-foundation-context
Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.
catchup
Restore context after /clear by summarizing recent work and project state.
codify-lesson
Detect recurring P2/P3 audit patterns across recent rounds and promote them into lesson cards. Use after round boundaries or when repeated findings appear.
lane-memory
SMA-style project fact corpus under .agents/memory/. Opt-in via adoc stages.memory.enabled. Use when user says память, lane-memory, corpus, CORE, почему бот забыл, or an agent needs durable non-code facts. Not PROGRESS/LESSONS dumps.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.