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/cxcscmu/skilllearnbench/data-matchingnpx skills add cxcscmu/SkillLearnBench --skill data-matchinggit clone --depth 1 https://github.com/cxcscmu/SkillLearnBenchWhat 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.00017 | $0.01278 |
| Opus 5 | $0.00009 | $0.00639 |
| Sonnet 5 | $0.00003 | $0.00256 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
data-matching 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Matching Skill
Overview
Successfully matching observations to simulations requires careful handling of datetime and depth coordinates. The matching must use exact values with proper rounding—no interpolation or nearest-neighbor approximation.
Observation Data Format
CSV with columns:
datetime,depth,temp,OXY_oxy
2009-01-21 12:00:00,0,0.1,16.3
2009-01-21 12:00:00,1,0.7,16.3
...
- datetime: ISO format timestamp
- depth: Measured depth in meters
- temp: Water temperature in °C
- OXY_oxy: Oxygen (not used for temperature RMSE)
Simulation Output Characteristics
GLM output:
- Time dimension: Regular hourly intervals from simulation start
- Depth dimension: Variable number of layers based on model dynamics
- Temperature: Simulated at each time step and depth layer
Exact Matching Algorithm
Step 1: Load Observations
import pandas as pd
obs_df = pd.read_csv('/root/field_temp_oxy.csv')
obs_df['datetime'] = pd.to_datetime(obs_df['datetime'])
Step 2: Round Depths
Round observation depths to nearest meter (standard practice):
obs_df['depth_rounded'] = obs_df['depth'].round(0)
Step 3: Extract Simulation Data
import netCDF4 as nc
from netCDF4 import num2date
ds = nc.Dataset('/root/output/output.nc')
temp_sim = ds.variables['temp'][:] # [time, depth]
z_sim = ds.variables['z'][:] # depth coordinates
time_sim = ds.variables['time'][:] # time values
# Convert time to datetime
time_var = ds.variables['time']
dates_sim = num2date(time_sim, time_var.units)
ds.close()
Step 4: Exact Matching
def exact_match(obs_df, temp_sim, z_sim, dates_sim):
"""
Match observations to simulation using exact datetime and rounded-depth
Returns: aligned arrays of simulated temps, observed temps,
and metadata for filtering
"""
import numpy as np
matched = {
'sim_temp': [],
'obs_temp': [],
'depth': [],
'datetime': [],
'obs_idx': []
}
for idx, row in obs_df.iterrows():
obs_date = row['datetime']
obs_depth = row['depth_rounded']
obs_temp = row['temp']
# Find time index: exact datetime match
time_idx = None
for i, sim_date in enumerate(dates_sim):
if sim_date == obs_date:
time_idx = i
break
if time_idx is None:
continue # No exact datetime match
# Find depth index: exact depth match
depth_idx = None
for j, sim_z in enumerate(z_sim):
if np.isclose(sim_z, obs_depth, atol=0.01):
depth_idx = j
break
if depth_idx is None:
continue # No exact depth match
# Record match
matched['sim_temp'].append(temp_sim[time_idx, depth_idx])
matched['obs_temp'].append(obs_temp)
matched['depth'].append(obs_depth)
matched['datetime'].append(obs_date)
matched['obs_idx'].append(idx)
return matched
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 · 186 lines · 17 tokens per session scan A e707bfce746d
data-matching is a skill published in the GitHub repository cxcscmu/SkillLearnBench (82 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,278 once invoked, about $0.0001 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
creating-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Letta Code's capabilities with specialized knowledge, workflows, or tool integrations.
Context Doctor
Identify and repair degradation in system prompt, external memory, and skills preventing you from following instructions or remembering information as well as you should.
image-generation
Generate images from text prompts (and optionally edit/remix input images). Use when the user asks to create, generate, draw, render, or edit an image, illustration, logo, icon, diagram, or photo.
adding-models
Guide for adding new LLM models to Letta Code. Use when the user wants to add support for a new model, needs to know valid model handles, or wants to update model-specific compatibility behavior. Covers runtime catalog sources, CI test matrices, and handle validation.
hotpath_init
Configure hotpath profiling in a Rust project. Adds the hotpath dependency with feature-gated setup, instruments main with hotpath::main, functions with measure/measureall, and wraps channels, mutexes, rwlocks, streams, futures, reqwest clients, axum routers and byte-level I/O with hotpath macros. Use when the user…
writing-bench-task-judge
Use when writing or modifying checkgoals() / getanswer() / App check methods in benchenv/task/, or when reviewing a draft task's judge correctness. Triggers include adding a new task, editing a judge method, or diagnosing a judge false-positive/negative.