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/kdr/overcast/overcast-timelinenpx skills add kdr/overcast --skill overcast-timelinegit clone --depth 1 https://github.com/kdr/overcastWrote 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/kdr/overcast/overcast-timeline)<a href="https://agentmods.dev/skills/kdr/overcast/overcast-timeline"><img src="https://agentmods.dev/badge/skills/kdr/overcast/overcast-timeline.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 | $0.00036 | $0.00683 |
| Opus 5 | $0.00018 | $0.00342 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
overcast-timeline 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
overcast-timeline
Use this skill to "walk through what happened" across several recordings of one
event (bystander videos, multiple cameras, a sequence of clips): build one ordered,
cited timeline and flag where accounts disagree. Use the broad overcast skill and
overcast/reference/verbs.md for exact flags.
Workflow
- Sense every clip —
watchfor the visual timeline,listenwhere audio carries the account:
overcast doctor --json
overcast case init --json
overcast watch ./cam1.mp4 --json
overcast watch ./phone-clip.mp4 --json
overcast listen ./phone-clip.mp4 --json
- Cross-anchor shared moments with span notes — a visible clock, a shared sound, a lighting change lets you line clips up on one timeline:
overcast note "wall clock reads 21:14 as the door opens" --ref <cam1-record-id> --at 12-15 --tag anchor --json
overcast note "same doorbell chime as cam1@13 — clips overlap here" --ref <phone-record-id> --at 3-6 --tag anchor --json
- Corroborate and contradict across clips. File a conflict finding ONLY when the answer actually reports a disagreement — don't invent one every run; if the accounts agree, record that and skip the finding:
overcast ask "order the events across all clips with timestamps; where do accounts agree or conflict? cite record.id + media.at" --json
# only if the answer reports a real conflict:
overcast finding create "conflict: cam1 shows the car arriving BEFORE the shout; phone-clip audio has the shout first" --ref <cam1-record-id> --at 12-15 --confidence low --json
- Produce the chronological deliverable, and always leave a
tldrnote first:
overcast note "reconstructed <n> clips into one timeline; <k> firm anchors; <c> unresolved conflicts" --tag tldr --json
# Wait for the note result before exporting, so the TL;DR is included.
overcast brief --export ./timeline.html --json
Output
One ordered chronology of the event, each entry cited to a record.id + media.at,
the anchor moments that let clips be aligned, and an explicit list of unresolved
contradictions. Where clips can't be ordered relative to each other, say so rather
than guessing.
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.
- 5d ago First seen · 69 lines · 36 tokens per session scan A e934aa8d3157
overcast-timeline is a skill published in the GitHub repository kdr/overcast (16 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 683 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
video-to-skill
Turn a video, tutorial, playlist, or course into an installed, evidence-grounded course Skill that can teach, give practice and feedback, apply demonstrated methods, and answer reference questions. Use when the user provides video sources and wants reusable learning or operational capability.
frame-light-leak-cinema
Film light leaks, grain, 16:9 letterbox, and large serif type for cinematic openings or chapter cards.
osmedeus-expert
Expert guide for the Osmedeus security automation workflow engine. Use when: (1) writing or editing YAML workflows (modules and flows), (2) running osmedeus CLI commands (scan, workflow management, installation, server), (3) configuring steps, runners, triggers, or template variables, (4) debugging workflow execution…
recon-tool-integration
Adding a new tool to the recon pipeline: the enrichment-module contract and its isolated wrapper (the actual fan-out and test call path), graph completeness, and the preset catalog that silently strips unknown settings. Miss the isolated wrapper and the tool never runs in parallel; miss the catalog and AI presets drop…
supply-chain-scan
Working on RedAmon's supply-chain scanner (offline OSV + GuardDog + retire + trufflehog): the offline OSV database that the scan path does not bootstrap, the world-readable requirement for the hardened scanner, and the soft-error markers that record what was never analysed. Trigger: editing…
frame-glitch-title
数字故障 / 像散偏移 / 数据腐败标题, 适合视频转场 / cyberpunk hero.