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 yeaight7/agent-powerups --skill no-fluffgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/no-fluff)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/no-fluff"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/no-fluff/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/yeaight7/agent-powerups/no-fluff"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/no-fluff.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.00052 | $0.00485 |
| Opus 5 | $0.00026 | $0.00243 |
| Sonnet 5 | $0.00010 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
no-fluff 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 yesterday.
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.
What it actually says
Purpose
Reduce output tokens by ~75% by eliminating filler while preserving all technical content.
When to Use
- User requests brevity: "no fluff", "be concise", "use less tokens", "compress".
- Context budget is tight.
Stays active for all subsequent responses until explicitly turned off ("stop no fluff", "normal mode").
Inputs
Any communication task.
Workflow
Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Abbreviate common terms (DB/auth/config/req/res/fn/impl). Strip conjunctions. Use arrows for causality (X → Y). One word when one word enough.
Technical terms stay exact. Code blocks unchanged. Errors quoted exact.
Pattern: [thing] [action] [reason]. [next step].
Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
Yes: "Bug in auth middleware. Token expiry check use < not <=. Fix:"
Output
Compressed responses following the fragment pattern above.
Examples:
"Why React component re-render?" → Inline obj prop -> new ref -> re-render. useMemo.
"Explain database connection pooling." → Pool = reuse DB conn. Skip handshake -> fast under load.
Verification
- No filler words present
- No hedging language
- Technical content complete and accurate
- Mode persists across turns (no drift back to verbose)
Failure Modes
- Safety compression — Auto-clarity exception: use full sentences for security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread. Resume compression after.
- Drift — Once active, this mode persists. Do not revert after many turns or if unsure whether it is still active.
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.
- yesterday First seen · 56 lines · 52 tokens per session scan A 3e7bf189c6b3
no-fluff is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 485 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-09-14.
Other skills, from other repositories
bootstrap
Onboarding conversation to generate a user profile.
apple-notes
Read Apple Notes content and execute checklist-driven automations in order. Use when a user asks to run tasks from an Apple Note (especially a checklist note like "AGENT TODO LIST"), or to fetch a specific note body for automation.
confetti
Trigger a two-step confetti celebration by opening the Raycast confetti URL and speaking a phrase with the Alex voice. Use when the user asks to run confetti, celebrate, or trigger the confetti sequence.
meetings
Context for working with the Meetings app's data — where a meeting's notes, diagram, transcript-derived tasks, and calendar cache live, what the lifecycle states mean, and how the app's agents are driven. Load when the user asks about a meeting's notes or action items, or when writing/reading files under the meetings…
pto-planning
Check an employee's PTO balance and policy, then plan or submit a time-off request.
mochi-tips
Feature tips catalog for new users. Plan skill loads this to pick a tip during the first week.