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 gabonio/agent-operator-toolkit --skill marketplace-managementgit clone --depth 1 https://github.com/gabonio/agent-operator-toolkitWrote 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/gabonio/agent-operator-toolkit/marketplace-management)<a href="https://agentmods.dev/skills/gabonio/agent-operator-toolkit/marketplace-management"><img src="https://agentmods.dev/badge/skills/gabonio/agent-operator-toolkit/marketplace-management/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/gabonio/agent-operator-toolkit/marketplace-management"><img src="https://agentmods.dev/badge/skills/gabonio/agent-operator-toolkit/marketplace-management.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.00074 | $0.00664 |
| Opus 5.5 | $0.00030 | $0.00266 |
| Sonnet 5.5 | $0.00015 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
marketplace-management 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 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.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketplace Management
Treat marketplace registries, plugin manifests, and the Gemini extension manifest as an integrity boundary. Read repository instructions and the target plugin before changing them.
Classify the task
- Add plugin: scaffold a self-contained
plugins/<name>/root and append registry entries. - Update plugin: change the owning plugin, bump its version, and synchronize shared metadata.
- Validate: remain read-only and report drift, malformed metadata, unsafe paths, or missing assets.
- Release: regenerate when supported, validate, review the complete diff, and publish only authorized changes.
- Setup problem: route user installation and discovery issues to an available setup or doctor skill.
Add or update a plugin
- Discover the marketplace root and read its contributor instructions.
- Prefer an available plugin scaffolder over hand-creating schema-sensitive manifests.
- Keep the outer directory and manifest
nameidentical, lowercase, and hyphenated. - Keep plugin content self-contained. Use relative paths beginning with
./and do not depend on sibling checkouts or machine-specific locations. - Maintain
.claude-plugin/plugin.jsonand.codex-plugin/plugin.json. Shared identity fields must agree; Codex-only interface fields stay in the Codex manifest. - Append matching entries to both marketplace registries without reordering or replacing unrelated plugins.
- Include explicit Codex installation, authentication, and category policy.
- Validate each
SKILL.md, the plugin manifest, the marketplace registries, and referenced assets. - Keep Gemini's root
skills/entrypoints and TOML commands synchronized with their authoritative plugin skills.
Release discipline
- Use semantic versioning and never publish changed plugin or extension content under an existing version.
- If the repository has a generator, edit its declared source of truth and regenerate; do not hand-edit generated outputs.
- Run the repository's strict check—
./scripts/checkin Agent Operator—then inspect Git status for generated drift and unrelated changes. - Confirm install and update documentation matches the current marketplace name and repository URL.
- Do not install, stage, commit, push, or publish unless the user authorized that action.
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.
- 1mo ago First seen · 50 lines · 74 tokens per session scan A 625ae4b2aa17
marketplace-management is a skill published in the GitHub repository gabonio/agent-operator-toolkit (1 stars, last pushed 7d ago), licensed MIT. It adds 74 tokens to every session and 664 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…