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/telagod/code-abyss/mlnpx skills add telagod/code-abyss --skill mlgit clone --depth 1 https://github.com/telagod/code-abyssWhat 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.00114 | $0.00573 |
| Opus 5 | $0.00057 | $0.00287 |
| Sonnet 5 | $0.00023 | $0.00115 |
| Haiku 4.5 | $0.00011 | $0.00057 |
Grade A, and why
ml 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 2d 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
ML — approach, data, evals, LLM craft, traps
Rule content lives in the five files below; this SKILL.md only routes
(doctrine/04-maintenance.md governs edits to this bundle too).
Route by moment
| You are about to… | Read (in this folder) |
|---|---|
| Decide whether ML/an LLM is warranted, and which method rung to use | approach.md |
| Touch a dataset, labels, or splits; suspect a score is too good | data.md |
| Define success, build/judge an eval, or assess someone's metric claim | evals.md |
| Build with LLMs: prompts, RAG, structured output, agents, model choice | llm.md |
| Diagnose an underperforming model or LLM feature | data.md §1 first (read real failures), then llm.md §3 if RAG, traps.md to name the pattern |
| Review an ML project's health; name why a claim or pipeline smells wrong | traps.md |
A new ML feature usually runs approach.md (interrogate + pick the rung) →
evals.md §1 (eval BEFORE build) → data.md → then llm.md if the rung is LLM-shaped
→ skim traps.md §C before finalizing any launch or monitoring plan.
Scope and neighbors
Modeling and evaluation judgment. The serving infrastructure around a model is ordinary
backend (backend bundle: APIs, queues, operate.md); experiment execution discipline is
methods (investigate/verify); whether to delegate → doctrine.
The stance
The eval is the spec; anything unmeasured is folklore. Look at the data with your
own eyes (data.md §1), climb the method ladder from the cheapest rung (approach.md
§3), and treat every surprising score as leakage until disproven (data.md §2). The
failure mode of this field is not bad models — it is unearned confidence in numbers.
What ships with it
5 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.
- 2d ago First seen · 39 lines · 114 tokens per session scan A 8396ad545ca3
ml is a skill published in the GitHub repository telagod/code-abyss (240 stars, last pushed 1mo ago), licensed MIT. It adds 114 tokens to every session and 573 once invoked, about $0.0006 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
codexkit-a-b-test-planner
Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.
codexkit-api-design-reviewer
Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.
codexkit-architecture-decision-writer
Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.
codexkit-audit-readiness-checker
Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when…
codexkit-business-case-writer
Write structured business cases with problem framing, options analysis, financial modeling (NPV/ROI/Payback), risk assessment, and implementation roadmap. Follows HBR business case structure. Use when seeking budget approval, proposing new initiatives, or justifying investment decisions.
codexkit-campaign-brief-writer
Write agency-standard creative briefs for marketing campaigns. Structure Background, Objective (SMART), Target Audience persona, Key Message, Mandatories, KPIs, Timeline, and Budget Allocation. Use when briefing agencies, creative teams, or internal marketing on a new campaign.