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 vasilyu1983/AI-Agents-public --skill ai-coding-agents-pluginsgit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/ai-coding-agents-plugins)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/ai-coding-agents-plugins"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/ai-coding-agents-plugins.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 246 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- medium Agent Snooping · line 205 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- low Privilege Escalation · line 90 Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
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.00040 | $0.06130 |
| Opus 5 | $0.00020 | $0.03065 |
| Sonnet 5 | $0.00008 | $0.01226 |
| Haiku 4.5 | $0.00004 | $0.00613 |
Grade B, and why
ai-coding-agents-plugins 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 8d 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.
| `user` | `~/.claude/settings.json` | Personal, all projects (default) | How it starts
The opening of the file, as written. The whole thing — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Agents Plugins
Use this skill to design or review plugin systems for coding-agent runtimes, especially terminal-first CLIs that load skills, hooks, MCP servers, commands, agents, or output styles from installable extensions.
This skill owns plugin architecture for coding agents. For the broader coding-agent creation workflow, start with ../ai-coding-agents/SKILL.md.
ASCII Flow
plugin package
|
v
manifest validation
identity + version + capability declarations + trust class
|
v
install or load
built-in | user | project | marketplace | repo-local
|
v
registration
skills + commands + tools + hooks + agents + MCP servers
|
v
policy filter + namespace
only safe capabilities enter the runtime
|
v
reload/disable/uninstall invalidates caches and visible registries
Quick Reference
| Question | Read | Outcome |
|---|---|---|
| How should a coding-agent plugin be structured? | references/plugin-manifest-and-capability-model.md |
Package layout, manifest fields, capability families |
| How should plugins load, reload, and register? | references/plugin-loading-and-runtime-lifecycle.md |
Discovery order, activation flow, cache and reload rules |
| Where should trust boundaries live? | references/plugin-trust-boundaries-and-safety.md |
Install-time safety, runtime restrictions, policy controls |
| How does OpenAI Codex structure plugin manifests and marketplace lifecycle? | references/openai-codex-plugin-manifest-and-marketplace.md |
Skills/MCP/apps/hooks paths, interface metadata, path rules, marketplace add/remove/upgrade |
| How does GitHub Copilot CLI structure plugin manifests and marketplaces? | references/github-copilot-cli-plugin-manifest-and-marketplace.md |
Manifest search order, component paths, marketplace.json shape, install sources, cross-runtime manifest convergence with Claude Code |
What ships with it
11 files 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.
- agents/openai.yaml 279 B
- assets/templates/plugin.manifest.template.json 1.6 KB
- data/sources.json 6.7 KB
- learnings.consolidated.md 600 B
- learnings.md 494 B
- references/github-copilot-cli-plugin-manifest-and-marketplace.md 6.0 KB
- references/openai-codex-plugin-manifest-and-marketplace.md 2.6 KB
- references/plugin-loading-and-runtime-lifecycle.md 4.7 KB
- references/plugin-manifest-and-capability-model.md 7.0 KB
- references/plugin-trust-boundaries-and-safety.md 4.8 KB
- scripts/validate_manifest.py 9.9 KB runs code
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.
- 8d ago First seen · 356 lines · 40 tokens per session scan B f5a959ea5f08
ai-coding-agents-plugins is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (86 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 6,130 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
plan-validate
Deterministic plan.json validation via Python script, replacing most plan-validator agent calls. Performs JSON parsing, schema validation, task checkbox regex, required section checks, sync validation, and data extraction. Only semantic consistency checks (storage/query alignment) require the LLM agent. Triggers on…