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/kdevos12/alkyl/active-learningnpx skills add Kdevos12/ALKYL --skill active-learninggit clone --depth 1 https://github.com/Kdevos12/ALKYLWhat 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.00063 | $0.00770 |
| Opus 5 | $0.00032 | $0.00385 |
| Sonnet 5 | $0.00013 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
active-learning 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Active Learning for Drug Discovery
Purpose
Closed-loop molecular optimization: iteratively query the most informative compounds, label with assay/oracle, retrain model. Accelerates hit-to-lead and lead optimization by minimizing wet-lab experiments.
When to Use This Skill
- Building a surrogate model to replace expensive docking/assay calls
- Running a DMTA (Design-Make-Test-Analyze) loop
- Accelerating virtual screening with AL-ranked acquisition
- Combining QSAR uncertainty with experimental prioritization
Reference Files
Load specific references on demand:
| File | Content |
|---|---|
references/al-theory.md |
Query strategies, acquisition functions, convergence, pool vs stream |
references/molecular-al.md |
Molecular representations, batch AL, diversity-reweighted sampling |
references/uncertainty-integration.md |
GP/conformal/ensemble signals → acquisition, calibration |
references/docking-al.md |
Surrogate docking oracle, VS acceleration, Logloss/BEDROC metrics |
references/dmta-loop.md |
Full DMTA cycle, stopping criteria, experiment prioritization, case studies |
Quick Routing
"I want to find actives with fewest assay calls"
→ al-theory.md (query strategy) + molecular-al.md (batch AL)
"I want to accelerate a docking campaign"
→ docking-al.md (surrogate oracle)
"I have GP/conformal uncertainty, want to plug into AL loop"
→ uncertainty-integration.md
"I'm running a real DMTA cycle with a CRO"
→ dmta-loop.md
Core Loop Pattern
# Canonical active learning loop
labeled_pool = initial_dataset # seed: 50–200 diverse cpds
unlabeled_pool = virtual_library # 10k–1M candidates
for round in range(n_rounds):
model.fit(labeled_pool.X, labeled_pool.y)
scores = acquisition_fn(model, unlabeled_pool.X) # uncertainty / EI / UCB
batch = select_batch(unlabeled_pool, scores, k=batch_size)
labels = oracle(batch) # assay / docking / human expert
labeled_pool = labeled_pool + (batch, labels)
unlabeled_pool = unlabeled_pool - batch
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 · 71 lines · 63 tokens per session scan A e8d19859110b
active-learning is a skill published in the GitHub repository Kdevos12/ALKYL (6 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 770 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
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.