json-file-processing

json-file-processing is a skill for Claude Code, Codex from cxcscmu/SkillLearnBench. It costs 21 tokens per session (383 once invoked), scanned A, original, MIT.

A guide to reading email requests from a JSON file and creating reply files plus a results file. JSON is a structured text format for storing and exchanging data.

In plain words
What is it for?
Use it to process meeting-scheduling requests, save replies as text files, and produce a JSON summary of the results.
Why use it?
It turns a repeated file-processing task into a predictable workflow with recorded recipients and output filenames.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to process meeting-scheduling requests, save replies as text files, and…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cxcscmu/skilllearnbench/json-file-processing
Install

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.

Any agent
npx skills add cxcscmu/SkillLearnBench --skill json-file-processing
Clone the repo
git clone --depth 1 https://github.com/cxcscmu/SkillLearnBench

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for json-file-processing

README.md
[![agentmods](https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/json-file-processing.svg)](https://agentmods.dev/skills/cxcscmu/skilllearnbench/json-file-processing)
Your own site
<a href="https://agentmods.dev/skills/cxcscmu/skilllearnbench/json-file-processing"><img src="https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/json-file-processing.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 383 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00383
Opus 5 $0.00010 $0.00192
Sonnet 5 $0.00004 $0.00077
Haiku 4.5 $0.00002 $0.00038

Measured 3d ago against content hash 114766f03404, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

json-file-processing 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 3d 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.

skills/b1-one-shot-claude-sonnet-4-6/schedule-planning/json-file-processing/SKILL.md · 55 lines

What it actually says

JSON File Processing for Meeting Scheduler

Reading Input

import json

with open("/root/test_input.json") as f:
    emails = json.load(f)

# Each item has: email_text, from_email
for i, email in enumerate(emails, start=1):
    msg_id = i
    text = email["email_text"]
    sender = email["from_email"]

Writing Reply Files

def save_reply(msg_id, content):
    filename = f"/root/reply_{msg_id}.txt"
    with open(filename, "w") as f:
        f.write(content)
    return f"reply_{msg_id}.txt"

Writing results.json

results = {
    "sent_results": [
        {"filename": f"reply_{msg_id}.txt", "recipient": sender}
        for msg_id, sender in ...
    ]
}
with open("/root/results.json", "w") as f:
    json.dump(results, f, indent=2)

Date Formatting Rules

  • Day name: full name, e.g. "Monday"
  • Month: full name, e.g. "March"
  • Day: zero-padded two digits, e.g. "09"
  • Year: four digits, e.g. "2026"
  • Example: "Monday, March 09, 2026"

Time Formatting Rules

  • Hours: zero-padded two digits, e.g. "09", "10", "11"
  • Minutes: zero-padded two digits, e.g. "00", "30"
  • Period: "AM" or "PM"
  • Example: "09:00 AM - 10:30 AM"
Changes

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.

  1. 3d ago First seen · 55 lines · 21 tokens per session scan A 114766f03404

Subscribe to this mod's changes

json-file-processing is a skill published in the GitHub repository cxcscmu/SkillLearnBench (83 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 383 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-09-03.