change-event-timeline

change-event-timeline is a skill for Claude Code, Codex from fzfclee/consulting-skills. It costs 50 tokens per session (720 once invoked), scanned A, original, Apache-2.0.

A method for arranging events in time to identify turning points and possible causes. It compares the situation before and after a change and records the people, behaviors, decisions, or measurements involved.

In plain words
What is it for?
Use it to analyze changes in behavior, decisions, relationships, metrics, or risk. It helps build an event sequence, identify causal candidates, and define questions for verification.
Why use it?
It prevents old background facts from being confused with recent triggers. This makes it easier to investigate what changed and which event may matter.

Skill for Claude CodeCodex

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

Good fit Use it to analyze changes in behavior, decisions, relationships, metrics, or risk. It helps build an event sequence, identify causal candidates, and define questions for verification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fzfclee/consulting-skills/change-event-timeline
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 fzfclee/consulting-skills --skill change-event-timeline
Clone the repo
git clone --depth 1 https://github.com/fzfclee/consulting-skills

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 change-event-timeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/fzfclee/consulting-skills/change-event-timeline/github.svg)](https://agentmods.dev/skills/fzfclee/consulting-skills/change-event-timeline)
Your own site
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/change-event-timeline"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/change-event-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.

agentmods 80×15 button for change-event-timeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/change-event-timeline"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/change-event-timeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 720 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.00050 $0.00720
Opus 5 $0.00025 $0.00360
Sonnet 5 $0.00010 $0.00144
Haiku 4.5 $0.00005 $0.00072

Measured 12d ago against content hash 72299d6b5bad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

change-event-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 12d 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/change-event-timeline/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Change Event Timeline

Use this skill to find what changed, when it changed, and which change most likely matters.

Method Notes

  • Many diagnoses fail because they treat all facts as equally current.
  • A timeline helps distinguish long-standing background facts from recent trigger events.
  • The goal is to identify turning points, causal candidates, and validation questions.

Required Inputs

Collect or infer these inputs before execution:

  • situation or decision question
  • key events and dates or approximate sequence
  • before-state and after-state
  • stakeholders involved in each event
  • observed behavior, decision, metric, or risk change

If an input is missing, mark it as unknown, state the assumption used, and add a validation action.

When Not To Use

Do not use when timing is irrelevant or the decision is purely comparative. Use decision-matrix or weighted-scorecard instead.

Step-by-Step Execution

Step Required input How to execute Output
Define the before-state Baseline relationship, process, metric, or expectation. Describe the stable pattern before the relevant change. Baseline state.
Build event list Dates, approximate sequence, stakeholder actions, decisions. Put events in chronological order; include uncertainty when dates are approximate. Event timeline.
Mark turning points Event list, behavior or outcome change. Identify events after which behavior, risk, support, urgency, or outcome changed. Turning-point candidates.
Distinguish trigger vs background Timeline, evidence strength, alternative explanations. Separate events that merely existed from events that likely changed the system. Trigger/background classification.
Infer causal hypotheses Turning points, stakeholder moves, external events. Generate possible explanations that fit the timeline. Timeline-based hypotheses.
Define next evidence Weak links, unknown dates, missing stakeholder rationale. Specify what evidence would confirm or weaken the inferred turning point. Timeline validation plan.

Read the full file on GitHub · 80 lines

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. 12d ago First seen · 80 lines · 50 tokens per session scan A 72299d6b5bad

Subscribe to this mod's changes

change-event-timeline is a skill published in the GitHub repository fzfclee/consulting-skills (4 stars, last pushed 23d ago), licensed Apache-2.0. It adds 50 tokens to every session and 720 once invoked, about $0.0003 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-31.