Borrowing it
Nothing to install: this file belongs to mag123c/toktrack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mag123c/toktrack/main/.claude/skills/next/SKILL.mdgit 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/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/mag123c/toktrack/next"><img src="https://agentmods.dev/badge/skills/mag123c/toktrack/next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.5 | $0.00004 | $0.00148 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 64 lines · 11 tokens per session scan A c154a149c837
next is a skill published in the GitHub repository mag123c/toktrack (196 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 371 once invoked, about $0.0000 per session on Opus 5.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
microservices-architecture
Microservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
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.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
audio-production
Professional audio production for music, podcasts, and sound design. Use when working with audio recording, mixing, mastering, or sound design for any medium.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.