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/jshiv/cronicle/file-summarizernpx skills add jshiv/cronicle --skill file-summarizergit clone --depth 1 https://github.com/jshiv/cronicleWrote 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/jshiv/cronicle/file-summarizer)<a href="https://agentmods.dev/skills/jshiv/cronicle/file-summarizer"><img src="https://agentmods.dev/badge/skills/jshiv/cronicle/file-summarizer.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.1 | $0.00044 | $0.00368 |
| Opus 5 | $0.00022 | $0.00184 |
| Sonnet 5 | $0.00009 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
file-summarizer 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 6d 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
file-summarizer
When to use
Use this skill when you've been given a directory (typically via the
fs__list_directory and fs__read_text_file tools from the MCP
filesystem server) and the operator wants one summary covering all
of it, not file-by-file digests.
How to summarize
- One paragraph, 80–120 words. Resist the urge to bullet — this is a digest, not a manifest.
- Lead with the through-line. What do these files have in common? Where do they diverge? Open the paragraph with that frame.
- Name files inline when a specific file carries a key point.
Use the basename only (e.g.
release-notes.md), not the full path. - No meta commentary. Don't write "this directory contains…". Write the digest as if it were going into a status report.
Output format
Write to ${scratch}/SUMMARY.md with exactly this shape:
# File summary — <YYYY-MM-DD>
<one paragraph, 80–120 words>
---
_files_: <comma-separated basenames>
Replace <YYYY-MM-DD> with today's date and <comma-separated basenames>
with the file names you actually read.
When NOT to use
If the operator asks for "summaries" plural (one per file) or "what's in each file," do that instead — this skill is the single-paragraph variant.
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.
- 6d ago First seen · 50 lines · 44 tokens per session scan A ed362b9f65d0
file-summarizer is a skill published in the GitHub repository jshiv/cronicle (23 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 368 once invoked, about $0.0002 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
dagu
Authors, validates, and troubleshoots Dagu DAG definitions and assists with Dagu CLI operations. Use when creating or debugging DAG YAML, choosing Dagu commands, or inspecting and managing DAGs and runs from the CLI.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue"…
migrating-workflow-v4-to-v5
Upgrades an app from Workflow SDK 4.x to 5.0. Use when bumping the workflow / @workflow/ dependencies to v5, or when hitting removed v4 APIs — runStep, stepEntrypoint, workflow/internal/private, @workflow/core/private, writeToStream / closeStream / readFromStream on a World, world.steps.get without a runId…
migrating-world-v4-to-v5
Upgrades a custom Workflow SDK World implementation from the v4 spec to v5. Use when a package implements the World interface from @workflow/world and is moving to 5.x — event IDs that are ULIDs rather than slot positions, Event id is not slot-numbered at replay time, a specVersion the runtime refuses, writeToStream /…
migrating-to-workflow-sdk
Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(), step.waitForEvent(), Trigger.dev tasks / wait.forToken / triggerAndWait, ASL JSON state machines, Task/Choice/Wait/Parallel states, task tokens, or child workflows.