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/hoavdc/codexkit/codexkit-vendor-comparison-matrixnpx skills add hoavdc/CodexKit --skill codexkit-vendor-comparison-matrixgit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-vendor-comparison-matrix)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-vendor-comparison-matrix"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-vendor-comparison-matrix.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.00061 | $0.01279 |
| Opus 5 | $0.00030 | $0.00639 |
| Sonnet 5 | $0.00012 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
codexkit-vendor-comparison-matrix 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vendor Comparison Matrix
When to Use
- When evaluating 2+ vendors or tools for a purchase decision
- When building a business case for tool selection
- When leadership requires a structured evaluation for procurement
- When comparing build-vs-buy options
Procedure
Step 1 — Requirements Gathering
Categorize requirements:
| Category | Requirement | Priority (Must/Should/Nice) |
|---|---|---|
| Functional | [What it must do] | Must |
| Integration | [What it connects to] | Should |
| Security | [Compliance needs] | Must |
| Performance | [Speed, scale] | Should |
| Support | [SLA, response time] | Nice |
Identify deal-breakers — any Must requirement not met eliminates the vendor.
Step 2 — Weight Criteria
Assign weights that sum to 100:
| Category | Weight | Justification |
|---|---|---|
| Functionality | 30 | Core use case |
| Integration | 20 | Must connect to existing stack |
| Security & Compliance | 20 | Regulated industry |
| Pricing / TCO | 15 | Budget constrained |
| Vendor viability | 10 | Long-term relationship |
| UX / Adoption | 5 | Ease of rollout |
Step 3 — Score Vendors
Score each vendor 1–5 per criterion:
| Criterion (Weight) | Vendor A | Vendor B | Vendor C |
|---|---|---|---|
| Feature set (30) | 4 → 120 | 5 → 150 | 3 → 90 |
| Integration (20) | 5 → 100 | 3 → 60 | 4 → 80 |
| Security (20) | 4 → 80 | 4 → 80 | 5 → 100 |
| Pricing (15) | 3 → 45 | 2 → 30 | 5 → 75 |
| Viability (10) | 5 → 50 | 4 → 40 | 2 → 20 |
| UX (5) | 4 → 20 | 5 → 25 | 3 → 15 |
| Weighted Total | 415 | 385 | 380 |
Step 4 — TCO Analysis
Calculate Total Cost of Ownership over 3 years:
| Cost Component | Vendor A | Vendor B | Vendor C |
|---|---|---|---|
| License / subscription | $X | $Y | $Z |
| Implementation / migration | ... | ... | ... |
| Training & change management | ... | ... | ... |
| Ongoing support / maintenance | ... | ... | ... |
| Integration development | ... | ... | ... |
| Opportunity cost of downtime | ... | ... | ... |
| 3-Year TCO | $XX | $YY | $ZZ |
What ships with it
1 file 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.
- yesterday First seen · 154 lines · 61 tokens per session scan A 13c79f1cb4c4
codexkit-vendor-comparison-matrix is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 1,279 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-09-03.
Other skills, from other repositories
data_analyst
Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
cultivating-personas
Distills AI agent voice patterns from conversation into a Persona Voice Card v1.0 (self/user/language/register/emojipolicy/flourish only — no judgment-shaped fields), validates schema + content safety + differentiation, and routes contributions through the existing submission portal. Use when the user wants to…
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
detecting-and-responding
蓝队与紫队工程：检测规则编写、SIEM/EDR 调优、事件响应、数字取证、威胁狩猎、ATT&CK 映射、紫队演练闭环。Use when writing Sigma/YARA detection rules, tuning SIEM noise, responding to security incidents, conducting forensic analysis, hunting threats, or running purple team exercises.