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-toolsgit 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-tools)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/ai-coding-agents-tools"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/ai-coding-agents-tools/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/vasilyu1983/ai-agents-public/ai-coding-agents-tools"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/ai-coding-agents-tools.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.00038 | $0.04324 |
| Opus 5 | $0.00019 | $0.02162 |
| Sonnet 5 | $0.00008 | $0.00865 |
| Haiku 4.5 | $0.00004 | $0.00432 |
Grade A, and why
ai-coding-agents-tools 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 10d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Agents Tools
Use this skill to design or review the tool runtime of a coding-agent CLI: tool contracts, tool pool assembly, deferred loading, tool-search behavior, permission-aware execution, and remote rendering of tool results.
This skill owns tool-runtime architecture for coding agents. For command architecture, use ../ai-coding-agents-command-runtime/SKILL.md.
ASCII Flow
tool sources
built-ins + MCP + plugins + remote server + deferred catalog
LSP tools (activated when plugin supplies lspServers config; always-load semantics)
|
v
tool pool assembly
shared contract + stable ordering + mode filtering + deny-before-exposure
Agent(type) tool: parameterized by type discriminator gating spawnable subagent types
|
v
model-visible tools
always-loaded subset + ToolSearch discovery path
|
v
execution pipeline
validate -> permission -> hooks -> run -> shape result -> persist -> render
|
v
local or remote result
normalized into the same session message model
Quick Reference
| Question | Read | Outcome |
|---|---|---|
| How should tools be modeled and assembled? | references/tool-registry-and-pool-assembly.md |
Tool contract, built-in vs MCP pool, deny filtering, prompt-cache-stable ordering |
| How should deferred tools, execution, and remote results work? | references/deferred-loading-execution-and-remote-results.md |
ToolSearch, defer rules, execution pipeline, remote tool-result rendering |
| Should this tool be deferred or always-loaded? | references/deferral-eligibility-decision-tree.md |
Decision tree, criteria table, alwaysLoad vs shouldDefer, override settings |
| How do I implement the ToolSearch schema-load pattern? | scripts/toolsearch_schema_loader_example.py |
Annotated stdlib-only example: deferred pool, handler, reconnect, policy scope |
| How does OpenAI Codex model unified exec and composable CLI tools? | references/openai-codex-unified-exec-and-tool-contracts.md |
PTY sessions, stdin writes, output budgets, permission-aware params, CLI-wrapper pattern |
What ships with it
9 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 312 B
- data/sources.json 3.9 KB
- learnings.consolidated.md 598 B
- learnings.md 1.2 KB
- references/deferral-eligibility-decision-tree.md 7.5 KB
- references/deferred-loading-execution-and-remote-results.md 3.1 KB
- references/openai-codex-unified-exec-and-tool-contracts.md 3.2 KB
- references/tool-registry-and-pool-assembly.md 3.7 KB
- scripts/toolsearch_schema_loader_example.py 9.0 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.
- 10d ago First seen · 243 lines · 38 tokens per session scan A c3e621149b67
ai-coding-agents-tools is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 4,324 once invoked, about $0.0002 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-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.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".