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 skills/agentconfig/agentconfig.org/add-providernpx skills add agentconfig/agentconfig.org --skill add-providergit clone --depth 1 https://github.com/agentconfig/agentconfig.orgWrote 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/agentconfig/agentconfig.org/add-provider)<a href="https://agentmods.dev/skills/agentconfig/agentconfig.org/add-provider"><img src="https://agentmods.dev/badge/skills/agentconfig/agentconfig.org/add-provider.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 | $0.00055 | $0.01862 |
| Opus 5 | $0.00028 | $0.00931 |
| Sonnet 5 | $0.00011 | $0.00372 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
add-provider 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 4d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Provider
Add a new AI coding assistant provider to agentconfig.org's provider comparison system.
Overview
Adding a provider requires coordinated work across 6 parallel work streams:
| Stream | Work | Duration | Dependencies |
|---|---|---|---|
| 1. Type System | Add provider to union types | 2-4 hrs | None |
| 2. Data Layer | Add implementations for all 13 primitives | 4-6 hrs | Stream 1 |
| 3. UI Components | Update comparison table | 4-8 hrs | Streams 1-2 |
| 4. Testing | Update E2E tests | 3-4 hrs | Stream 3 |
| 5. App Integration | Update site copy & docs | 1-2 hrs | Streams 1-3 |
| 6. LLMs Generation | Regenerate machine-readable files | 1-2 hrs | All streams |
Total effort: ~2-3 hours with parallelization
When to Use
Use this skill when:
- Integrating a new coding assistant (Cursor, Claude Desktop, Zed with AI, etc.)
- Expanding provider support beyond current offerings
- The provider implements most of the 13 AI primitives
- You want comprehensive comparison data visible to users and AI agents
Prerequisites
Before starting, gather:
- Provider capability audit - Which of the 13 primitives does the provider support?
- File path documentation - Where do config files go (global vs project)?
- Support levels -
primitives.tsandcomparison.tsshare oneSupportLeveltype:full(native),partial(workarounds),diy(custom setup or not achievable) — one vocabulary, no separatenonevalue
The 13 Primitives
Every provider must map to all 13 primitives across the 8 layers below (layers are not 1:1 with primitives — Instructions has three, Memory & State currently has none); see categories in site/src/data/primitives.ts for the full layer list and scopeModel for the separate where-it-applies vocabulary — scopes are not primitives:
| Layer | Primitives |
|---|---|
| Instructions | Persistent Instructions, User Scope Instructions, Directory / Path Scope Instructions |
| Procedures | Skills / Workflows, Slash Commands |
| Tools & Context | Tool Integrations (MCP) |
| Delegation | Agent Mode, Custom Agents |
| Control & Approval | Permissions & Guardrails, Lifecycle Hooks, Runtime Sandbox |
| Memory & State | (reserved — no primitive is modeled here yet; do not add one without genuinely distinct memory/state semantics) |
| Distribution | Configuration Distribution |
| Verification & Observability | Verification / Evals |
What ships with it
6 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.
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.
- 4d ago First seen · 165 lines · 55 tokens per session scan A b8f7d16e2374
add-provider is a skill published in the GitHub repository agentconfig/agentconfig.org (8 stars, last pushed 7d ago), licensed ISC. It adds 55 tokens to every session and 1,862 once invoked, about $0.0003 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 skills, from other repositories
clinical-decision-support
Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading…
molecular-cloning
Molecular cloning simulation and design. PCR amplicon prediction, restriction enzyme digestion, Golden Gate and Gibson assembly simulation, primer design, CRISPR sgRNA design, and plasmid annotation. For protein-level sequence analysis use biopython or esm; for database lookups use gene-database or ensembl-database.
flow-cytometry-analysis
Complete flow cytometry analysis pipeline. FCS file handling, compensation, manual/automated gating, immunophenotyping, CFSE proliferation analysis, cell cycle analysis (Dean-Jett-Fox), and apoptosis assays. Extends flowio with analytical workflows. For raw FCS parsing only use flowio.
immunology-assays
Computational analysis of immunology experimental data. ATAC-seq differential accessibility, immune cell tracking from microscopy, ELISA data processing with 4-parameter logistic fitting, immunohistochemistry quantification, antibody titer analysis, and cell cycle phase duration estimation. For flow cytometry use…
datamol
Pythonic wrapper around RDKit with simplified interface and sensible defaults. Preferred for standard drug discovery including SMILES parsing, standardization, descriptors, fingerprints, clustering, 3D conformers, parallel processing. Returns native rdkit.Chem.Mol objects. For advanced control or custom parameters…
glycobiology
Glycosylation site prediction and glycobiology analysis. N-glycosylation motif finding, O-glycosylation hotspot prediction, glycan structure resources. Lightweight, pure Python. For protein function queries use uniprot-database; for structure analysis use alphafold-database.