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 anthonysuherli/br8n --skill timelinegit clone --depth 1 https://github.com/anthonysuherli/br8nWrote 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/anthonysuherli/br8n/timeline)<a href="https://agentmods.dev/skills/anthonysuherli/br8n/timeline"><img src="https://agentmods.dev/badge/skills/anthonysuherli/br8n/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.1 | $0.00098 | $0.00737 |
| Opus 5 | $0.00049 | $0.00368 |
| Sonnet 5 | $0.00020 | $0.00147 |
| Haiku 4.5 | $0.00010 | $0.00074 |
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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
br8n — Timeline (append-only activity log)
br8n periodically rolls this repo+branch's session notes, context captures, and
journal entries into a chronological, append-only timeline at
<project_path>/.br8n/timeline/:
all-time.md— the canonical append-only log (newest at the bottom, never rewritten).recent.md— the last few days (regenerated each pass).week.md— the past week (regenerated each pass).
This is the temporal view — distinct from /br8n:docs (the topical doc tree) and
/br8n:activity (the cross-repo work graph). The files are git-ignored and regenerated;
never hand-edit them — they rebuild from notes/captures/journal.
Step 0 — Resolve target
project = git repo basename, kb = git branch, project_path = repo root
(see ../_shared/preamble-first.md):
basename "$(git rev-parse --show-toplevel)" # project
git branch --show-current # kb
git rev-parse --show-toplevel # project_path
No prior tap needed — the timeline is plain files in the working tree.
Step 1 — Read and present
The timeline files are markdown on disk under <project_path>/.br8n/timeline/. Read
them with your own file tools — no MCP call needed to read:
Read<project_path>/.br8n/timeline/recent.mdand present it (newest at the bottom — the "scrolling down" feel).- Point the user at the wider views:
week.md(past week) andall-time.md(the full scroll).Readand surface those too if the user asks for more history.
If the dir is empty or missing, say so and offer --rebuild (Step 2) to build it
from the notes/captures/journal so far.
Step 2 — --rebuild (force a pass)
Trigger when the user passes --rebuild, or when the dir is empty/stale. Call:
mcp__plugin_br8n_br8n__br8n_timeline(
project, kb, project_path, force=true
)
It returns {forced, appended, recent_days, week_days, all_time_path, recent_path, week_path}. Report appended (how many new events landed in the all-time log) and the
window sizes, then re-read recent.md (Step 1) and present the refreshed view.
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.
- 8d ago First seen · 62 lines · 98 tokens per session scan A d153b73b2ab9
timeline is a skill published in the GitHub repository anthonysuherli/br8n (1 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 737 once invoked, about $0.0005 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.
Other skills, from other repositories
unforgit-memory
Use Unforgit MCP tools as durable repository memory for decisions, conventions, gotchas, and playbooks.
potpie-graph
Use when the task can read or write the project-memory graph through the potpie CLI: discover the contract with graph catalog, read named views with graph read, resolve entity identity with graph search-entities, create validated plans with graph propose, commit plans with graph commit --verify, inspect quality with…
pr-reviewer
Fetches PR review comments, analyzes requested changes, implements fixes, commits and pushes the resolution. Use after a reviewer has left comments on an open PR to close the feedback loop efficiently.
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.
release-prep
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.
learn
Diagnose and fix agent behavioral surfaces when the user corrects a mistake — connects to Claude native memory.