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.
git clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/commands/gosha70/code-copilot-team/providers)<a href="https://agentmods.dev/commands/gosha70/code-copilot-team/providers"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/providers.svg" alt="Measured on agentmods" 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.00000 | $0.00064 |
| Opus 5 | $0.00000 | $0.00032 |
| Sonnet 5 | $0.00000 | $0.00013 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
providers 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 3d 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.
What it actually says
Check LLM provider status and connectivity:
- Read configured provider environment variables
- For each configured provider, attempt a minimal health check (list models or ping)
- Report: provider name, status (connected/error), default model, estimated cost
- If no providers are configured, show setup instructions
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.
- 3d ago First seen · 6 lines · 0 tokens per session scan A 8c979c921a94
providers is a command published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 64 tokens. 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-09-03.
Other commands, from other repositories
discover
Discover runtime AI components and static AI dependencies with AIR Blackbox.
structured-output-doctor
Find LLM calls whose output is parsed as JSON and harden them with native structured output plus validate-and-retry.
rag-debug
Walk the 9-layer RAG failure diagnostic chain against a specific failing query.
rag-failure-trace
Capture a full RAG audit trace for a query — useful for debugging or seeding a regression test.
review-code
Review code for quality, security, and maintainability. Dispatches all relevant reviewer agents in parallel and merges findings by severity.
rag-audit
Report quality and best-practice gaps in an existing implementation. TRIGGER WHEN: the user asks to review, audit, or validate a RAG pipeline: chunking, embeddings, retrieval, reranking, or production readiness. DO NOT TRIGGER WHEN: building from scratch (use rag-architect), or auditing a pure vector database (use…