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 DavidROliverBA/ArchitectKB --skill timelinegit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/timeline)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/timeline"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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/davidroliverba/architectkb/timeline"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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.00000 | $0.00584 |
| Opus 5 | $0.00000 | $0.00292 |
| Sonnet 5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/timeline
Generate a chronological timeline for a project or topic using sub-agents.
Usage
/timeline <project or topic>
/timeline MyDataIntegration
/timeline NewProductLine
/timeline SAP migration
Instructions
Phase 1: Planning
- Identify the project/topic
- Load
.claude/context/projects.mdfor context - Plan to gather events from:
- Project file (key dates, milestones)
- Meetings (by date)
- ADRs (decision dates)
- Tasks (created, completed dates)
- Daily notes (mentions)
Phase 2: Parallel Gathering (use sub-agents)
Launch sub-agents in parallel using model: "haiku" for efficiency:
Agent 1: Project Milestones (Haiku)
- Read project file
- Extract: start date, key milestones, status changes
- Return: date, event type, description
Agent 2: Meeting Timeline (Haiku)
- Search
+Meetings/for all meetings linked to project - Extract: date, meeting title, key outcomes
- Return: chronological list
Agent 3: Decision Timeline (Haiku)
- Find ADRs related to project
- Extract: created date, status change dates, decision
- Return: decision events
Agent 4: Task Timeline (Haiku)
- Find tasks linked to project
- Extract: created date, due date, completed date
- Return: task lifecycle events
Phase 3: Compile Timeline
# Timeline: {{Project/Topic}}
**Generated**: {{DATE}}
**Span**: {{earliest date}} to {{latest date}} ({{duration}})
## Visual Timeline
{{YEAR}} ├── Q1 │ ├── Jan │ │ └── {{event}} │ ├── Feb │ │ └── {{event}} │ └── Mar ├── Q2 ...
## Detailed Timeline
### {{YYYY-MM}}
#### {{DATE}} - {{Event Title}}
- **Type**: Meeting / Decision / Milestone / Task
- **Details**: {{description}}
- **Outcome**: {{result if applicable}}
- **Link**: [[{{source note}}]]
### {{YYYY-MM}}
...
## Key Milestones
| Date | Milestone | Status |
|------|-----------|--------|
{{major milestones}}
## Decision Points
| Date | Decision | ADR |
|------|----------|-----|
{{decisions with links}}
## Activity Heatmap
{{show which months had most activity}}
## Gaps
{{identify periods with no documented activity}}
## Upcoming
{{future dated items if any}}
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.
- 9d ago First seen · 114 lines · 0 tokens per session scan A c885322449a4
timeline is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 584 tokens. 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.