What is no-trivial-wrappers?

A code-design rule against functions that only pass their arguments to another function without adding anything. Such forwarding functions are called trivial wrappers.

Use it when deciding whether to add a wrapper around an existing function, keeping one only when it adds a contract, adapts an interface, hides details, or satisfies a trait.

Redundant wrappers create extra names and layers without changing behavior, making code harder to follow.

no-trivial-wrappers — Cursor rule for Cursor by briangmilnes

Install

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.

Clone the repo

git clone --depth 1 https://github.com/briangmilnes/APAS-VERUS

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/briangmilnes/apas-verus/no-trivial-wrappers/github.svg)](https://agentmods.dev/rules/briangmilnes/apas-verus/no-trivial-wrappers)

Your own site

<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/no-trivial-wrappers"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/no-trivial-wrappers/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/no-trivial-wrappers"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/no-trivial-wrappers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 273 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00273
Opus 5	$0.00000	$0.00137
Sonnet 5	$0.00000	$0.00055
Haiku 4.5	$0.00000	$0.00027

Measured 7d ago against content hash eb5ee3609939, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

no-trivial-wrappers 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 7d 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.

.cursor/rules/style/no-trivial-wrappers.mdc · 41 lines

What it actually says

No Trivial Wrappers

Do not create wrapper functions that merely forward to another function without adding value.

Bad Example

fn n_plus(&self, v: &V) -> SetStEph<V> {
    parallel_n_plus(self.A.to_seq(), v.clone_plus())
}

fn n_minus(&self, v: &V) -> SetStEph<V> {
    parallel_n_minus(self.A.to_seq(), v.clone_plus())
}

If parallel_n_plus can be called directly, the wrapper adds nothing.

When Wrappers Are Justified

Wrappers are acceptable when they:

Add a spec/contract that the underlying function lacks
Adapt the interface (different parameter order, types, or defaults)
Hide implementation details (the inner function is private/internal)
Provide trait conformance (implementing a trait method)

Rule

Before creating fn2 that calls fn1:

Can callers just call fn1 directly?
Does fn2 add specs, adapt types, or satisfy a trait?

If fn2 adds nothing, eliminate it.

Changes

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.

7d ago First seen · 41 lines · 0 tokens per session scan A eb5ee3609939

Subscribe to this mod's changes

no-trivial-wrappers is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 273 tokens. 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-09-03.

Code review

no-trivial-wrappers

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

No Trivial Wrappers

Bad Example

When Wrappers Are Justified

Rule

What this file has done since we first saw it

Other cursor rules, from other repositories

clean-code-reviewer

sweep-benchmarks

code-review

ponytail

angular-20

dev-standard