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 future-architect/uzomuzo-oss --skill diet-evaluate-removalgit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWrote 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-evaluate-removal)<a href="https://agentmods.dev/skills/future-architect/uzomuzo-oss/diet-evaluate-removal"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/diet-evaluate-removal/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-evaluate-removal"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/diet-evaluate-removal.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.00017 | $0.03960 |
| Opus 5 | $0.00009 | $0.01980 |
| Sonnet 5 | $0.00003 | $0.00792 |
| Haiku 4.5 | $0.00002 | $0.00396 |
Grade A, and why
diet-evaluate-removal 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diet Removal Evaluation: $ARGUMENTS
Deep-dive evaluation of whether $ARGUMENTS is worth removing, using a 5-phase data-driven framework. This command picks up where uzomuzo diet leaves off -- diet gives you the priority ranking, this gives you the removal verdict.
When to use: After uzomuzo diet ranks a dependency and you need to decide whether to invest the effort. Works for any difficulty level -- trivial deps get a quick confirmation, hard deps get a concrete migration plan.
Relationship to other skills:
uzomuzo diettells you ranking and difficulty (automated, all dependencies at once)/diet-evaluate-removaltells you whether it's worth removing and how (LLM-powered, one dependency at a time)/diet-assess-risktells you how dangerous it is to keep (LLM-powered, security focus)/diet-removeexecutes the removal (LLM-powered, implementation)
Phase 1: Ingest Diet Data
Extract the target dependency's diet JSON entry. Prefer existing JSON over re-running diet.
Option A -- existing diet JSON (preferred):
jq '.dependencies[] | select(.name == "$ARGUMENTS")' diet.json
Option B -- run diet now:
uzomuzo diet --sbom bom.json --source . --format json | jq '.dependencies[] | select(.name == "$ARGUMENTS")'
Required fields to extract
Display ALL of these from the diet JSON. Do NOT re-compute any of them.
| Field | What it tells you |
|---|---|
name / version / ecosystem |
Dependency identity |
purl |
Canonical package URL identifier |
scope |
Dependency scope: "tool" (build-time-only), "runtime" (reflection/ServiceLoader-loaded) |
rank / priority_score |
Where this dep sits in the removal priority list |
difficulty |
trivial / easy / moderate / hard |
exclusive_transitive / total_transitive |
Deps removed together / total transitive count |
stays_as_indirect |
Whether it remains after removing direct usage |
indirect_via |
Which other deps pull it in transitively |
import_file_count |
Number of files importing this dep |
call_site_count |
Total call sites across all files |
api_breadth |
Number of distinct APIs used |
symbols |
Exact API surface used (function/type names) |
import_files |
Exact file paths that import this dep |
has_blank_import / has_dot_import / has_wildcard_import |
Special import patterns |
is_unused |
Whether diet detected zero imports |
lifecycle |
Active / Stalled / Legacy-Safe / EOL-Confirmed / EOL-Effective / EOL-Scheduled / Archived / Review Needed |
has_vulnerabilities / vulnerability_count / max_cvss_score |
Security signals |
overall_score |
Composite health score (OpenSSF Scorecard) |
graph_impact / coupling_effort / health_risk |
Score components |
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 · 279 lines · 17 tokens per session scan A 95bd60b318d9
diet-evaluate-removal is a skill published in the GitHub repository future-architect/uzomuzo-oss (32 stars, last pushed 2d ago), licensed Apache-2.0. It adds 17 tokens to every session and 3,960 once invoked, about $0.0001 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-01.
Other skills, from other repositories
clickup-cli
ClickUp CLI for managing tasks, sprints, comments, statuses, Docs, and archiving. Use when the user needs to interact with ClickUp — creating/editing/archiving tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Includes a generic clickup api passthrough covering…
daily-brief
Narrate FKF's deterministic daily control surface. Use when an owner asks to prepare the day, get a daily brief, or identify today's priorities and collection gaps.
rmine
Reference for the rmine CLI (Redmine client) — issue, time-tracking, and project commands, filter/name-matching semantics, and profile handling. Use when the user asks about Redmine issues, tickets, time logging, or projects.
ntm
Run NTM for multi-agent tmux orchestration, work triage, robot mode, safety, coordination, and local APIs. Use when spawning swarms, dispatching work, or operating ntm as an agent or human operator.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
follow-up-after-call
Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…