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 skills add markoblogo/abvx-agent-skills --skill lean-context-layoutgit clone --depth 1 https://github.com/markoblogo/abvx-agent-skillsWrote 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/markoblogo/abvx-agent-skills/lean-context-layout)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/lean-context-layout"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/lean-context-layout.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.1 | $0.00064 | $0.00551 |
| Opus 5 | $0.00032 | $0.00275 |
| Sonnet 5 | $0.00013 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
lean-context-layout 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 6d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lean Context Layout
Save tokens by changing what loads at startup. Keep the default context small, stable, and operational.
Goal
Separate:
- always-loaded essentials;
- on-demand reference material;
- archival history that should not auto-load.
Default Layout
Prefer a compact startup surface:
- top-level agent entry file with rules and pointers;
- quick-start commands;
- architecture map or repo map entrypoint;
- common mistakes or sharp edges;
- optional issue-specific or domain-specific notes loaded only when needed.
Everything else should move behind explicit paths in docs/, .claude/, docs/ai/, or equivalent repo-local structures.
Workflow
- Measure the current startup burden:
- which files are always loaded;
- which of them are large, stale, duplicated, or historical;
- which content is needed every session versus occasionally.
- Identify the four startup essentials:
- how to work here;
- how to run or test;
- where the code lives;
- what recurring mistakes to avoid.
- Move long histories, completed tasks, old sessions, generated artifacts, and bulky narrative docs out of the always-loaded path.
- Replace bulky text with short index pointers:
- “for X, read Y”;
- “for domain map, open Z”;
- “for completed work, see archive path”.
- Keep startup files stable. Frequent churn reduces cache utility and raises reread cost.
- Re-measure after restructuring and report the delta.
Codex And agentsgen Guidance
- Keep
AGENTS.mdsmall and procedural. - Push deeper material into
docs/ai/or other explicit reference paths. - Prefer compact summaries over completed-session logs in startup files.
- Preserve enough orientation that a fresh agent can still start productively.
Guardrails
- Do not delete durable project knowledge; relocate and index it.
- Do not hide critical safety or production constraints in optional docs.
- Do not create six tiny files when one clear compact file would do.
- Do not optimize only for token count if navigability becomes worse.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 70 lines · 64 tokens per session scan A d04e43af1e6b
lean-context-layout is a skill published in the GitHub repository markoblogo/abvx-agent-skills (15 stars, last pushed 12d ago), licensed MIT. It adds 64 tokens to every session and 551 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ctx
Use ctx as working memory for prior agent work. Before starting or continuing work in an unfamiliar area, resuming earlier work, or revisiting an investigation, search prior sessions to ground yourself in earlier context. When ctx blame is available, use it to trace a line, file, commit, or PR to the agent session…
source-command-latch-seed
Preview and apply latch seed candidates from the exact current Cursor conversation. Use when the user invokes latch-seed or /latch-seed in Cursor.
krimto-write-fact
Use when the user asks you to remember something for later, save team knowledge, record a decision, or note a durable fact about the project, person, or team. Triggers on "remember that", "save this", "add to memory", "note for the team". Do not use for conversational context.
krimto-hierarchical-scope
Use when deciding what scope to store a fact at, or when reasoning about whether a fact applies to the current user. Krimto uses a user -> team -> org hierarchy with precedence rules. Triggers when scope selection is required.
krimto-recall-team
Use when starting a task, joining a conversation about a project, or before answering a question that needs team context. Triggers on "what do we know about X", "team's approach to Y", or before any domain-specific work.
project-knowledge-maintainer
Maintain a project-level knowledge base for coding agents using AGENTS.md, knowledge files, bug memory, decisions, and changelog records.