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 gustavo-meilus/aiboarding --skill more-with-lessgit clone --depth 1 https://github.com/gustavo-meilus/aiboardingWrote 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/gustavo-meilus/aiboarding/more-with-less)<a href="https://agentmods.dev/skills/gustavo-meilus/aiboarding/more-with-less"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/aiboarding/more-with-less/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/gustavo-meilus/aiboarding/more-with-less"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/aiboarding/more-with-less.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.00085 | $0.01769 |
| Opus 5 | $0.00043 | $0.00885 |
| Sonnet 5 | $0.00017 | $0.00354 |
| Haiku 4.5 | $0.00009 | $0.00177 |
Grade A, and why
more-with-less 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 9d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
More With Less Engineering
Use this Skill as the default design and implementation lens for non-trivial project work.
The objective is not minimum code, files, tokens, tools, agents, or tests independently. The objective is the minimum sufficient system that reliably satisfies the real requirements and preserves required guarantees.
Core doctrine
Do the least that fully solves the real problem. Use the least powerful sufficient mechanism. Keep active context, authority, tools, state, agents, handoffs, and orchestration as small as practical. Preserve the guarantees that matter. Hide unavoidable complexity behind stable interfaces. Add complexity only when evidence shows the simpler system is insufficient, and remove it when that evidence no longer holds.
Mandatory operating rules
- Understand before simplifying. Inspect the relevant code, docs, behavior, callers, constraints, and existing guarantees before choosing the smaller solution.
- Solve the real requirement. Prefer outcome and acceptance criteria over user-prescribed implementation choreography unless the implementation method is itself a requirement.
- Delete or reuse before adding. Prefer existing project capability, language/runtime facilities, native platform behavior, installed dependencies, and deterministic scripts before new machinery.
- Use the least powerful sufficient mechanism. Prefer deterministic code, schemas, tests, linters, type systems, DB constraints, and scripts before model judgment or orchestration when they can decide the property reliably.
- Keep context progressive. Load only the information required for the current decision. Do not dump the whole repository, spec corpus, or this full playbook into context without need.
- One agent by default. Add a reviewer/specialist only for independent judgment, context isolation, different authority, specialized expertise, or useful parallelism.
- Minimize the tool and permission surface. Give the current task only the capabilities needed to understand, act, observe, and verify.
- Make specification proportional. Spec depth grows with uncertainty, consequence, and coordination. Do not force proposal/design/task ceremony onto trivial work.
- Make verification proportional. Use the minimum evidence sufficiently strong for the consequence of failure. Keep the oracle stronger than the generator.
- Never simplify away critical guarantees. Preserve trust-boundary validation, security, authorization, data integrity, accessibility, irreversible-operation safeguards, required architecture invariants, acceptance criteria, rollback/recovery, necessary observability, and explicit requirements.
- Prefer root-cause fixes. For bugs, reproduce when feasible, trace the real path, and fix the shared cause rather than patching symptoms repeatedly.
- Design for deletion. For non-trivial new harness or architecture mechanisms, know why they exist, what would prove them insufficient, and what would allow them to be removed.
What ships with it
3 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.
- 9d ago First seen · 193 lines · 85 tokens per session scan A 4e5b74309008
more-with-less is a skill published in the GitHub repository gustavo-meilus/aiboarding (2 stars, last pushed 12d ago), licensed MIT. It adds 85 tokens to every session and 1,769 once invoked, about $0.0004 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
setup-rootloom
Plan, install, inspect, update, or roll back Rootloom Personal Core in a user's Codex home. Supports Skills-only, guidance, and the recommended personal preset. Use when the user explicitly asks for a Rootloom setup plan, installation, configuration, bootstrap, repair, audit, status, update, reduction, rollback, or…
project-memory
Initialize, retrieve, and explicitly update the separate Rootloom Memory plugin's repository-owned architecture, risk, decision, and failure lessons. Use only when explicitly requested. Memory is experimental, advisory, and outside Rootloom Core.
project-guidance
Create, refine, or validate repository guidance on explicit user request; preserve real-path scope, managed ownership, and unrelated content.
operating-coding-change
Complete scoped code changes with proportional verification; load governed, Evidence, and external-action procedures only when needed.
operating-code-review
Review without editing; report evidence-backed defects by severity and disclose material verification gaps.
dayu-harness
A one-time deployment tool that adds a project governance system built around AGENTS.md, project instructions, documentation, hooks, continuous integration, and maintenance scripts.