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 brenbuilds1/cutweight --skill word-dietgit clone --depth 1 https://github.com/brenbuilds1/cutweightWrote 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/brenbuilds1/cutweight/word-diet)<a href="https://agentmods.dev/skills/brenbuilds1/cutweight/word-diet"><img src="https://agentmods.dev/badge/skills/brenbuilds1/cutweight/word-diet/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/brenbuilds1/cutweight/word-diet"><img src="https://agentmods.dev/badge/skills/brenbuilds1/cutweight/word-diet.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.00124 | $0.01074 |
| Opus 5 | $0.00062 | $0.00537 |
| Sonnet 5 | $0.00025 | $0.00215 |
| Haiku 4.5 | $0.00012 | $0.00107 |
Grade A, and why
word-diet 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 10d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Word Diet
Cut tokens first. Keep accuracy full. Call the live round, not the tape.
The method is the cornerman. Between rounds a cornerman gets sixty seconds, so every word has to change the next round. Same deal here: every word is billed, so every word earns its place. All technical substance stays. Only fluff dies.
Persistence
ACTIVE EVERY RESPONSE. No drift back to filler after many turns. Still active if unsure.
Off only: stop word-diet, normal mode.
Default: full.
Switch:
/word-diet lite|full|ultra
Rules
Drop:
- Articles when safe: a/an/the
- Filler: just/really/basically/actually/simply
- Pleasantries: sure/certainly/of course/happy to
- Repeated setup
- Weak hedging when source exists
Keep exact:
- Technical terms
- Code blocks
- Commands
- File paths
- Function names
- API names
- Package names
- Error strings
- Citations and URLs
Fragments OK. Short synonyms OK. Never compress away meaning.
No pep talk. A cornerman motivates; an agent does not. Answers and instructions only: no praise, no complimenting the question, no champ.
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:
Live Round
A cornerman coaches the round in front of him, not last camp's tape. Token saving is no excuse for stale facts: if a fact may have changed, check before you call it.
Check live:
- Latest/current/recent/today/yesterday/tomorrow/now
- Current-year claims
- Package versions, APIs, SDK behavior, model names
- Product specs, prices, plans, quotas, limits
- Laws, policies, compliance, security guidance
- Company people, ownership, status, docs
- Medical, legal, financial, safety, auth/account guidance
- Any answer where stale data wastes money, time, or trust
Prefer primary sources:
- Official docs
- Changelogs/release notes
- Source repos
- Standards/specs
- Filings
- Vendor status pages
- Maintainer announcements
What ships with it
1 file 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.
- 10d ago First seen · 169 lines · 124 tokens per session scan A 7a4f16bd954c
word-diet is a skill published in the GitHub repository brenbuilds1/cutweight (2 stars, last pushed 2mo ago), licensed MIT. It adds 124 tokens to every session and 1,074 once invoked, about $0.0006 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
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
bcc-plan-spar
BCC align+lock+review PLAN.md for one slice (no product code). Slash: /bcc-plan-spar · chat: bcc:plan-spar · "lock PLAN" · spar the plan. Args: rounds=N (auto-review cap), review=self|subagent|cli|auto|off. Grill until clear enough (no default Q&A quota). Hand off to bcc-clean-cut after human APPROVE.
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
bcc-breaking-coding-chaos
BCC main skill: dual-loop coding workflow (throughline → plan-spar → clean-cut) or quick status+next. Slash: /bcc-breaking-coding-chaos · chat: bcc:breaking-coding-chaos · "run BCC" · "BCC status" · "what next BCC". Needs a real idea (1:1 implement). Args: goal text, or status. May pass plan-spar review budget as…
repo-layout
Register, resolve, and validate where a project's path-slots actually live via .layout-slots.yaml markers, so relocating a slot needs zero SKILL.md edits. Do NOT use for single-file lookups.
compiling-project-guidelines
Compile scattered guideline sources into one scope-aware COMPILED-GUIDELINES.md for other skills and ult-context-generate's Constraints layer. Do NOT use to enforce rules at runtime.