Borrowing it
Nothing to install: this file belongs to IgorGanapolsky/openclaw-console. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/IgorGanapolsky/openclaw-console/develop/.agents/skills/improve-codebase-architecture/SKILL.mdgit clone --depth 1 https://github.com/IgorGanapolsky/openclaw-consoleWrote 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/igorganapolsky/openclaw-console/improve-codebase-architecture)<a href="https://agentmods.dev/skills/igorganapolsky/openclaw-console/improve-codebase-architecture"><img src="https://agentmods.dev/badge/skills/igorganapolsky/openclaw-console/improve-codebase-architecture/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/igorganapolsky/openclaw-console/improve-codebase-architecture"><img src="https://agentmods.dev/badge/skills/igorganapolsky/openclaw-console/improve-codebase-architecture.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.00043 | $0.00536 |
| Opus 5.5 | $0.00017 | $0.00214 |
| Sonnet 5.5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
improve-codebase-architecture 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 27d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve Codebase Architecture
Use this skill before proposing or implementing architecture refactors in OpenClaw Console.
Required Reading
- Read
CONTEXT.mdfor OpenClaw domain language. - Read relevant ADRs in
docs/adr/. - Read the relevant local architecture docs:
docs/architecture.mddocs/protocol.md- platform README files when touching iOS or Android
Vocabulary
Use the architecture vocabulary from CONTEXT.md:
- Module
- Interface
- Implementation
- Depth
- Shallow Module
- Adapter
- Locality
- Leverage
Use OpenClaw domain terms from CONTEXT.md instead of inventing alternatives. For example, say Gateway, Skill, Task, Incident, Approval Request, Gateway Connection, Store Release, and Daily Active Approver.
Process
- Explore the area being changed.
- Identify friction:
- understanding one concept requires bouncing through many files
- a module interface is almost as complicated as its implementation
- policy, error handling, or release evidence is scattered across callers
- tests cover helper functions but miss the real interface
- a stable domain concept is missing from
CONTEXT.md
- Apply the deletion test:
- if deleting a module makes complexity disappear, it was probably pass-through code
- if deleting a module scatters complexity into callers, the module has value
- Present or implement only high-leverage changes:
- improve locality
- reduce caller knowledge
- make the interface a better test surface
- preserve mobile-thin-client and gateway-owned intelligence
- improve release read-back evidence or operator trust
Output For Architecture Reviews
When asked to review architecture, list candidates with:
- Files
- Problem
- Proposed change
- Benefit in locality, leverage, and testability
- ADR conflict, if any
Do not propose broad rewrites. Prefer small changes that make one module deeper.
Updating Context
If a real OpenClaw domain concept is missing, update CONTEXT.md in the same PR. If a decision should stop future agents from re-suggesting a rejected design, add an ADR under docs/adr/.
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.
- 27d ago First seen · 76 lines · 43 tokens per session scan A d245bdd82ffd
improve-codebase-architecture is a skill published in the GitHub repository IgorGanapolsky/openclaw-console (6 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 536 once invoked, about $0.0002 per session on Opus 5.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-10-02.
Other skills, from other repositories
defect-hunting
Use when reviewing code, auditing an app, writing a guard rule or test, or certifying any threshold/constant/formula. Finds the defects a diff review structurally cannot see — the second write path, the mis-calibrated constant, the rule that cannot fail. Triggers from code-reviewer, /app-audit, qa-engineer…
role-activation
Use at project start — /app-init, /app-onboard, or /app-run's first step — to decide which of the roles this product actually needs, and to write the durable roster the rest of the flow reads. Triggers whenever a command is about to fan out to a team, or a gate is about to run for a role that may not be on this…
mutation-testing
Use when adding or reviewing a gate, guard rule, CI grep, or test assertion in this plugin's own scripts — and whenever a suite is green and you need to know whether that means anything. Runs scripts/mutate.sh, which breaks the code on purpose and reports which assertions failed to notice. Triggers from code-reviewer…
architecture-builder
Use to produce the technical architecture doc and engineering principles for a mobile app. Used primarily by the CTO agent. Triggers on "design the architecture", "pick the stack", or as part of /app-plan.
accessibility-gate
Use as a pass/fail gate on any diff with a user-facing surface — by code-reviewer during review, by qa-engineer during the test pass, and by any IC before claiming a UI ticket done. This is the gate the plan called for instead of an accessibility specialist role. Triggers whenever a screen, component or state changes.
business-model
Use when deciding or revisiting how the product makes money — pricing, tiers, trial shape, ad load, unit economics — by ceo when setting the model, by cpo when a scope decision turns on revenue, and by product-researcher when investigating willingness to pay. A pricing analysis is a document, not a standing role.