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 skills add screenpipe/screenpipe --skill screenpipe-incident-timelinegit clone --depth 1 https://github.com/screenpipe/screenpipeWrote 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/screenpipe/screenpipe/screenpipe-incident-timeline)<a href="https://agentmods.dev/skills/screenpipe/screenpipe/screenpipe-incident-timeline"><img src="https://agentmods.dev/badge/skills/screenpipe/screenpipe/screenpipe-incident-timeline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/screenpipe/screenpipe/screenpipe-incident-timeline"><img src="https://agentmods.dev/badge/skills/screenpipe/screenpipe/screenpipe-incident-timeline.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00174 |
| Opus 5.5 | $0.00008 | $0.00070 |
| Sonnet 5.5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
screenpipe-incident-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 13d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 13d ago First seen · 13 lines · 21 tokens per session scan A 85bad1bc6a6f
screenpipe-incident-timeline is a skill published in the GitHub repository screenpipe/screenpipe (21,954 stars, last pushed today), with no licence file. It adds 21 tokens to every session and 174 once invoked, about $0.0001 per session on Opus 5.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-10-03.
Other skills, from other repositories
trulens-diagnosis
Diagnose low evaluation scores and generate actionable improvement recommendations.
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
resolve-author-fix
Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.