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 jameslowman/planning-with-james --skill go-timegit clone --depth 1 https://github.com/jameslowman/planning-with-jamesWrote 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/jameslowman/planning-with-james/go-time)<a href="https://agentmods.dev/skills/jameslowman/planning-with-james/go-time"><img src="https://agentmods.dev/badge/skills/jameslowman/planning-with-james/go-time/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/jameslowman/planning-with-james/go-time"><img src="https://agentmods.dev/badge/skills/jameslowman/planning-with-james/go-time.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.00023 | $0.06879 |
| Opus 5 | $0.00012 | $0.03439 |
| Sonnet 5 | $0.00005 | $0.01376 |
| Haiku 4.5 | $0.00002 | $0.00688 |
Grade A, and why
go-time 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 — 712 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Time: Execute the Plan
NON-NEGOTIABLE: ALL PATHS ARE RELATIVE TO THE REPO ROOT
All .claude/planning-with-james/ paths in this skill are relative to the current working directory (the repo you're working in), NOT ~/.claude/. The knowledge graph and plans live inside the project, not in your home directory. If you're unsure, run pwd to confirm you're in the repo root.
This skill implements a plan's tasks one at a time with rigorous state tracking. Every action is recorded to files so work survives autocompact, session breaks, and context loss.
One rule above all: read the files, trust the files, update the files.
NON-NEGOTIABLE #1 (RECORD): After completing each task, you MUST update context_scratch_pad.md, check off the task in tasks.md, and update _plan_state.json BEFORE starting the next task. This is the RECORD step (Step 4). A task is not done until the record is written. Skipping this step destroys the ability to recover from context loss.
NON-NEGOTIABLE #2 (SESSION-SCOPED): Your session ID is $CLAUDE_SESSION_ID. All plan activations in the registry are scoped to this session. When reading _registry.json, look up sessions["$CLAUDE_SESSION_ID"] for YOUR active plan. Do not touch other sessions' entries. Multiple terminals can work on different plans simultaneously.
NON-NEGOTIABLE #3 (KNOWLEDGE-FIRST): When you need to understand unfamiliar code during implementation - whether for a task, a deviation, debugging, or research - read the knowledge graph BEFORE exploring source files. The knowledge graph at .claude/planning-with-james/knowledge/ already contains module boundaries, key files, interfaces, patterns, and gotchas. Starting from source code wastes time rediscovering documented information. Read _overview.md, then _graph.json, then relevant module _index.md files. THEN fill gaps from source. When spawning subagents, include the relevant knowledge file paths in their prompt.
Arguments
$ARGUMENTS controls behavior:
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 · 712 lines · 23 tokens per session scan A b02676a89398
go-time is a skill published in the GitHub repository jameslowman/planning-with-james (2 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 6,879 once invoked, about $0.0001 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…