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 agentmods add instructions/gabonio/agent-operator-toolkit/agents-mdgit clone --depth 1 https://github.com/gabonio/agent-operator-toolkitWhat 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 | $0.00614 | $0.00614 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
agent-operator-toolkit AGENTS.md 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 yesterday.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Operator Marketplace AGENTS
These instructions apply anywhere this toolkit is checked out.
AGENTS.md is the canonical instruction source for this repo. The CLAUDE.md, CODEX.md, and GEMINI.md compatibility files point back here instead of containing divergent rules.
Purpose
This repo is a portable multi-agent marketplace for reusable AI-development plugins and skills. Keep distribution infrastructure generic, keep each plugin self-contained under plugins/, and use native Codex, Claude Code, and Gemini CLI surfaces.
Project-specific requirements, credentials, proprietary systems, employer names, and business rules belong in the project or private plugin that owns them, not here.
Read Order
Before changing this repo:
- read README.md
- read WORKFLOWS.md for plugin or release work
- read the target plugin's
SKILL.mdand directly referenced guidance
Scope
Track changes here only for:
- reusable, organization-neutral plugins under
plugins/ - Codex and Claude Code marketplace registries
- Gemini CLI extension metadata, commands, and skill entrypoints
- marketplace contributor documentation
- lightweight validation and release automation
Do not track:
- project-specific business logic
- vendored application or business-logic source unrelated to a marketplace plugin
- secrets or credentials
- machine-specific operational notes
- employer-specific review bots, internal commands, or proprietary platform guidance
- generated reports or scratch outputs
Plugin boundaries
- the target project owns product requirements and project-specific instructions
- each plugin owns only its reusable workflow and references
- marketplace root files own discovery, validation, and publishing behavior
- do not make one plugin depend on an organization-only bot, slash command, or service
Documentation Governance
Use the docs like this:
- README.md: marketplace usage and structure
- WORKFLOWS.md: plugin addition and release workflows
.claude-plugin/marketplace.json: Claude Code marketplace registry.agents/plugins/marketplace.json: Codex marketplace registrygemini-extension.json,commands/, andskills/: Gemini CLI extension surfaceplugins/: installable plugin roots- scripts/check: marketplace validation
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.
- yesterday First seen · 71 lines · 614 tokens per session scan A 612e537337c3
agent-operator-toolkit AGENTS.md is an instructions file published in the GitHub repository gabonio/agent-operator-toolkit (1 stars, last pushed 28d ago), licensed MIT. It adds 614 tokens to every session, about $0.0031 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.