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 agentmods add skills/mag123c/toktrack/nextnpx skills add mag123c/toktrack --skill nextgit clone --depth 1 https://github.com/mag123c/toktrackWrote 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/mag123c/toktrack/next)<a href="https://agentmods.dev/skills/mag123c/toktrack/next"><img src="https://agentmods.dev/badge/skills/mag123c/toktrack/next.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.00011 | $0.00371 |
| Opus 5 | $0.00005 | $0.00186 |
| Sonnet 5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
next 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 6d 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.
What it actually says
Next
Flow
Read Planning → Git Log → Analyze → Present → Suggest /clarify
Execution
-
Read Planning
# Read ONLY the latest planning file (by date prefix YYYYMMDD-) # e.g., 20260205-improvements.md > 20260128-cli-parsers.md # Check checkbox status: [ ] incomplete, [x] complete -
Git Log
git log --oneline -5 git status --short -
Analyze
- Identify current phase
- Count completed/total tasks
- Identify next priority task
-
Present (table format)
Phase Status Progress Phase 0 ✅ 5/5 Phase 1 🔄 3/4 -
Suggest
- Summarize next task
- Suggest running
/clarify
Output Format
## Current Status
- Phase: {current_phase}
- Progress: {completed}/{total} tasks
## Next Task
**{task_id}: {task_name}**
{brief_description}
## Action
Run `/clarify` to start: {task_summary}
Rules
- Read only the latest dated planning file (highest YYYYMMDD- prefix)
- If no planning files → infer from git log + code state
- Keep output concise (5-10 lines)
- Always suggest /clarify connection
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.
- 6d ago First seen · 64 lines · 11 tokens per session scan A c154a149c837
next is a skill published in the GitHub repository mag123c/toktrack (188 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 371 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-30.
Other skills, from other repositories
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.