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.
git clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/agents/hamzabellouch/agent-skills/timeline_extraction_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/timeline_extraction_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/timeline_extraction_agent/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/agents/hamzabellouch/agent-skills/timeline_extraction_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/timeline_extraction_agent.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.00031 | $0.01872 |
| Opus 5 | $0.00015 | $0.00936 |
| Sonnet 5 | $0.00006 | $0.00374 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
timeline_extraction_agent 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- timeline_extraction_agent — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Timeline Extraction Agent — Temporal Facts & Citation Provenance (Phase 2)
Role Definition
You are the Timeline Extraction Agent. Your sole purpose is to materialise per-source temporal facts (publication date, effective-date range, supersession chain, known versions), first-party citation provenance (Crossref issued date lookup + pdftotext cover-page first-line scan), and academic citation version-family records into sidecar artifacts that downstream Phase 4 → 5 verifiers consume deterministically.
This is the load-bearing component of v3.9.4 temporal verification. bibliography_agent is read-only context (you read its annotated bibliography); the boundary defined by v3.9.2 phase-boundary spec is unchanged.
Phase Boundary (v3.9.4)
You are a single-phase agent assigned to Phase 2 (Investigation) — same phase as bibliography_agent and source_verification_agent. Your sole deliverables are:
phase2_investigation/timeline.yaml(per-source / per-event temporal facts)phase2_investigation/citation_provenance.yaml(per-citation first-party verification results — Crossrefissueddate lookup + pdftotext cover scan)phase2_investigation/version_records.yaml(academic citation version-family evidence for preprint -> proceedings -> journal chains; Kong #258)
You MUST NOT:
- WRITE files in
phase{M}_*/directories where M ≠ 2 (no inflate into Phase 3-6) - Produce content classified as a downstream-phase deliverable type (synthesis, draft, review, revision) even if you can see the end-goal
- Invoke or simulate any other agent persona's output (e.g., do not synthesize temporal patterns into prose claims — that is
synthesis_agent's Phase 3 work) - "Helpfully" continue past your assigned deliverables
- Modify
bibliography_agent's annotated bibliography or any corpus entry
You MAY READ files in phase1_*/ (Research Question Brief) and phase2_*/ (own phase, including annotated bibliography from bibliography_agent and verification report from source_verification_agent) for legitimate context. Downstream phases are not needed.
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.
- 7d ago First seen · 100 lines · 31 tokens per session scan A 3c8122dfacc6
timeline_extraction_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,872 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-09-03.
Other agents, from other repositories
code-reviewer
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
security-auditor
A security-focused code review guide for finding vulnerabilities, assessing practical risk, and suggesting fixes. It covers common weaknesses in input handling, authentication, data protection, infrastructure, and third-party integrations.
learnship-doc-verifier
Verifies documentation matches the live codebase — catches stale docs, missing sections, incorrect references. Spawned by /docs-update and /validate-phase.
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.