Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/future-architect/uzomuzo-ossnpx agentmods add skills/future-architect/uzomuzo-oss/diet-removeWrote 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/future-architect/uzomuzo-oss/diet-remove)<a href="https://agentmods.dev/skills/future-architect/uzomuzo-oss/diet-remove"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/diet-remove/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/future-architect/uzomuzo-oss/diet-remove"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/diet-remove.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.07882 |
| Opus 5.5 | $0.00009 | $0.03153 |
| Sonnet 5.5 | $0.00004 | $0.01576 |
| Haiku 4.5 | $0.00002 | $0.00788 |
Grade A, and why
diet-remove 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 4d 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 — 581 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diet Remove: $ARGUMENTS
Analyze and plan the removal of dependency $ARGUMENTS, then take action.
Mode selection
- Default (Issue mode): Run Phase 1 analysis, then file a GitHub Issue with the findings and proposed migration plan. Appropriate for external OSS contributions and large projects where you don't own the build environment.
--pr(PR mode): Run the full removal lifecycle locally: analysis → replacement → verification → commit. Use this only when you own the project and can run build/test locally.
Parse $ARGUMENTS for flags, and set TARGET to the dependency itself: drop the flags and their values, and turn a PURL into the name the package manager uses (pkg:golang/github.com/pkg/[email protected] -> github.com/pkg/errors, pkg:npm/%40scope/[email protected] -> @scope/name). Every command below uses $TARGET, never the raw $ARGUMENTS.
Flags:
- If
--pris present → PR mode (direct implementation) - If
--repo owner/repois present → target that repository for the issue - Otherwise → Issue mode (default)
When to use: After /diet-evaluate-removal confirms the dependency is worth removing, or when uzomuzo diet reports it unused or easy (a "trivial" label is only meaningful if coupling was measured -- when every dependency shows trivial and none is unused, re-run diet with the right --source).
Safety principle: Every removal must pass build + vet + test before committing. If any step fails, stop and diagnose — don't force it.
Ecosystem detection
Detect the ecosystem from the PURL scheme or module path (pkg:golang/ → Go, pkg:npm/ → npm, pkg:pypi/ → Python, pkg:maven/ → Maven, pkg:cargo/ → Rust, pkg:githubactions/ → GitHub Actions). Diet measures source coupling for Go, Python, JavaScript/TypeScript, and Java only; for other ecosystems, find the import sites yourself before trusting a "trivial" or "unused" label.
If the ecosystem is not Go, display this notice to the user before proceeding:
Note: This skill's PR-mode commands and common patterns are optimized for Go. Issue mode and IBNC safety checks work for any language, but ecosystem-specific PR-mode guidance (verification commands, edge cases, lockfile handling) is still being developed for {ecosystem}. If you discover surprises or improvements during this removal, please contribute them via an issue or PR to future-architect/uzomuzo-oss.
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.
- 4d ago Changed · +4 lines 9224a9c0f05d
- 8d ago Changed · +42 lines 005e113cb783
- 1mo ago First seen · 535 lines · 22 tokens per session scan A 41089dae63fd
diet-remove is a skill published in the GitHub repository future-architect/uzomuzo-oss (42 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 7,882 once invoked, about $0.0001 per session on Opus 5.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-01.
Other skills, from other repositories
product
Consolidated Galyarder Framework Product intelligence bundle.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.