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 jamesdawsonWD/mooboard-skills --skill mooboard-create-timelinegit clone --depth 1 https://github.com/jamesdawsonWD/mooboard-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/skills/jamesdawsonwd/mooboard-skills/mooboard-create-timeline)<a href="https://agentmods.dev/skills/jamesdawsonwd/mooboard-skills/mooboard-create-timeline"><img src="https://agentmods.dev/badge/skills/jamesdawsonwd/mooboard-skills/mooboard-create-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/jamesdawsonwd/mooboard-skills/mooboard-create-timeline"><img src="https://agentmods.dev/badge/skills/jamesdawsonwd/mooboard-skills/mooboard-create-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.00051 | $0.01183 |
| Opus 5 | $0.00026 | $0.00592 |
| Sonnet 5 | $0.00010 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
mooboard-create-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 10d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mooboard Create Timeline
Create a new board under the Mooboard library as a chronological timeline on an infinite board.
Core idea
Events progress clearly left→right (default) or top→bottom. Each event is a cluster: date/label + image or evidence + short note. Whitespace separates eras; the infinite canvas can extend as long as needed.
Do not rely on a layout script. Use multi-agent review.
Best use cases
- Project / product roadmaps
- Company or personal history
- Trip day-by-day sequences
- Launch plans
- Process narratives (research → build → ship)
Style rules
Usually includes:
- a title and time-range subtitle
- 4–12 event clusters along an axis
- optional era headers (“Q1”, “Day 2”, “Before / After”)
- short notes and 0–1 image per event
- optional todo for next milestones
- sparse arrows only to show sequence when helpful
It should not look like a collage, masonry wall, or comparison matrix.
Layout character
Desired feel
- Readable chronology
- Even rhythm along the axis
- Clear event clusters
- Room to add future events further along the canvas
Default pattern
Horizontal timeline
- Title at top-left
- Baseline / axis implied by aligned event tops (y shared) or a thin geo line
- Event clusters at increasing x
- Optional summary / next steps at the far right
Spacing expectations
- Gap between event clusters: 160–280px
- Gap within an event cluster: 60–120px
- Hard minimum gap between substantial boxes: 60px
Required multi-agent workflow
Agent 1 — Narrative Planner
Orders events and chooses horizontal vs vertical.
Agent 2 — Region Planner
Assigns x/y zones per event and title/summary regions.
Agent 3 — Layout Planner
Sizes images/notes and stacks each event cluster.
Agent 4 — Collision Auditor
Checks no overlaps and that chronology reads unambiguously.
Agent 5 — Story Critic
Checks whether a stranger can follow the sequence in under 10 seconds.
Final Manifest Reviewer
Checks the written .mooboard.json:
- coordinates match the approved plan
- every image is
presentation: "interactive" - every link is
previewMode: "card"withpreviewImage - folder media matches referenced paths exactly
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.
- 10d ago First seen · 172 lines · 51 tokens per session scan A b2bdd030d042
mooboard-create-timeline is a skill published in the GitHub repository jamesdawsonWD/mooboard-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,183 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…