Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sukoji/loadout/plugin install loadoutWrote 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/sukoji/loadout/recommend)<a href="https://agentmods.dev/skills/sukoji/loadout/recommend"><img src="https://agentmods.dev/badge/skills/sukoji/loadout/recommend/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/sukoji/loadout/recommend"><img src="https://agentmods.dev/badge/skills/sukoji/loadout/recommend.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.00051 | $0.02516 |
| Opus 5.5 | $0.00020 | $0.01006 |
| Sonnet 5.5 | $0.00010 | $0.00503 |
| Haiku 4.5 | $0.00005 | $0.00252 |
Grade B, and why
recommend scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
merge into `./.codex/config.toml` under `[mcp_servers.<id>]`: use `command`/`args`/`env` for stdio and How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loadout — recommend and apply
Your job: look at THIS project, figure out what it is, and hand the user a short, ranked loadout of agent extensions worth adding — then apply exactly the ones they choose. You are a recommender and installer, not a list-dumper. Never paste the whole catalog.
Step 0 — Load the catalog (3 tiers)
Resolve the plugin root first from the directory two levels above this SKILL.md. A host-provided
PLUGIN_ROOT or CLAUDE_PLUGIN_ROOT may be used when available, but the workflow must not depend on
either variable. Refer to the resolved directory as <plugin-root> below.
Read the curated (Tier 1) files fully — they're small and hand-verified:
<plugin-root>/catalog/mcp.json<plugin-root>/catalog/skills.json<plugin-root>/catalog/hooks.json<plugin-root>/catalog/domains.json<plugin-root>/catalog/community.json(Tier 3, small)
Each item has id, name, description, domains, signals. MCP items carry a config, hook/setting
items a settings object, skill items an install block.
Tier 2 (official marketplace) is large (catalog/ecosystem.json, ~280 entries) — do NOT read it whole.
After you know the project's signals (Step 1), Grep ecosystem.json for those signal tokens to pull only
the handful of official plugins that match. Each is a tier: "official", verified Anthropic-marketplace
plugin installed with the /plugin install <name>@claude-plugins-official command in its install.commands.
Tier meaning: curated = auto-apply safe; official = trusted, install via /plugin; community
(Tier 3) = UNVERIFIED — only surface if the user asks to "discover"/see more, label it clearly, and never
auto-apply it. Items with "optIn": "token-saver" are never in discover or the domain loadout — offer
them only in the separate token-saver step (Step 3).
Step 1 — Profile the project
Detect what the repo is. Be fast and evidence-based — do not ask the user things you can read:
- Languages / frameworks / package managers: look for
package.json(and its deps — react, next, vue, svelte, express, nestjs, prisma…),requirements.txt,pyproject.toml,go.mod,Cargo.toml,pom.xml,Gemfile,pubspec.yaml,*.xcodeproj,build.gradle. - Infra / CI:
Dockerfile,docker-compose*,.github/workflows,*.tf,k8s/helm. - Data/ML:
*.ipynb,numpy/pandas/torch/tensorflowin deps,wandb/mlflow. - Research / academic:
*.tex,*.bib,papers/dir,arxivin deps. - Security surface: auth/payment/crypto libs, presence of
.env. - What's already set up: read existing
.mcp.json,.claude/settings.json,.claude/settings.local.json,.codex/config.toml,.codex/hooks.json,CLAUDE.md, andAGENTS.md. Never recommend something already installed.
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.
- 1mo ago First seen · 153 lines · 51 tokens per session scan B f7e7c20b1c14
recommend is a skill published in the GitHub repository sukoji/loadout (3 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 2,516 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
skillci-guardrails
Use this skill whenever you create, edit, or review a Claude Skill — any SKILL.md file, or the eval cases/config next to one. Most SKILL.md files today are written or edited by an agent, not typed by hand, so this closes the loop by having the agent that just wrote the skill also author it defensively and verify it…
example-skill
Writes a single changelog entry summarizing a code change, given a short description of what changed.
clean-skill
A skill with no lint issues, used as a starting point for the lint-on-type test.
skill-with-referenced-issue
Has a clean SKILL.md but an unsafe referenced script.
configuration
A guide to configuring OpenClaw, including its main YAML configuration file, environment variables, performance settings, and security options.
elasticsearch
Guidance for managing Elasticsearch, a search and data-storage system that organizes information into searchable indexes. It covers cluster health, nodes, shards, indexes, and related status APIs.