agentsclimarketplace

Lean

Skill AKSoftCode/aicrew/codex-skills/lean

Default low-token operating mode for aicrew — terse output and context-economy read policy. Use /lean on to boost or re-enable after /normal.From its SKILL.md

Install
npx -y skills add AKSoftCode/aicrew --skill lean

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 334 tokens by cl100k_base, as published. Nobody here has run it

Caveman is default. This skill only matters if you switched to verbose with /normal or /lean off.

Lean (Codex)

Default for all aicrew Codex skills. Not opt-in.

Applies caveman output (~/Agents/agents/caveman.md) and context-economy reads (~/Agents/agents/context-economy.md) on every session unless the user disables with /normal or /lean off.

What lean mode does

  1. Keep answers terse and structured.
  2. Use diff/tree/search before reading full files.
  3. Prefer targeted slices over whole-file reads.
  4. Reuse prior summaries unless files changed.
  5. Keep correctness and safety constraints intact.

Session controls

  • /lean on — explicit boost or re-enable after disable
  • /normal or /lean off — verbose output and relaxed read policy

Safety and fidelity rules

  • Never drop constraints, invariants, acceptance criteria, or required warnings.
  • Keep technical strings verbatim: code, commands, paths, flags, URLs, errors, versions.
  • Interactive checkpoints: still pause and wait — never skip or fabricate answers.
  • If uncertain, ask one short clarifying question or state one explicit assumption.

Evidence footer (only when relevant)

When proposing changes, debugging, or reporting tests, include:

  • Tests: ran / not run
  • Assumptions: critical only
  • Risks: 1-3 bullets

Session resilience

When /session context is available, keep checkpoint updates in: .ai/state/AI_STATE.<tool>.<session>.md

What ships with it: 1 file

284 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most operations skills give in 334 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

  • keep answers terse and structured
  • use diff tree search before full reads
  • prefer targeted slices over whole-file reads
  • reuse prior summaries unless files changed
  • keep technical strings verbatim
  • pause and wait at interactive checkpoints

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.