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/wasintoh/toh-framework/progress-trackingnpx skills add wasintoh/toh-framework --skill progress-trackinggit clone --depth 1 https://github.com/wasintoh/toh-frameworkWhat 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 | $0.00057 | $0.02090 |
| Opus 5 | $0.00028 | $0.01045 |
| Sonnet 5 | $0.00011 | $0.00418 |
| Haiku 4.5 | $0.00006 | $0.00209 |
Grade A, and why
progress-tracking 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 2d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📊 Progress Tracking Skill
Purpose: Visual progress tracking for users Version: 1.0.0 Author: Toh Framework Team
Overview
This skill enables AI to track and display project progress visually, so users always know where they are in the development journey.
Core Principle
User can always see:
- What's done ✅
- What's in progress ⏳
- What's remaining ⬚
- Estimated completion
TRANSPARENCY WITHOUT OVERWHELM
Progress Visualization Formats
Simple Progress Bar
🔄 **กำลังสร้าง:** ระบบร้านกาแฟ
[████████░░░░░░░░] 50%
✅ UI เสร็จแล้ว (4/4 หน้า)
⏳ Logic กำลังทำ (2/5 features)
⬚ Database ยังไม่เริ่ม
Detailed Phase View
📊 **Progress: ระบบร้านกาแฟ**
| Phase | Status | Progress |
|-------|--------|----------|
| 🎨 UI | ✅ Done | 100% |
| ⚙️ Logic | ⏳ In Progress | 60% |
| 🔌 Database | ⬚ Not Started | 0% |
| 🧪 Testing | ⬚ Not Started | 0% |
| 🚀 Deploy | ⬚ Not Started | 0% |
**Overall:** 40% complete
**Est. remaining:** ~2 hours
Feature Checklist View
📋 **Features Progress**
**POS System:**
- [x] หน้า POS
- [x] รายการสินค้า
- [x] ตะกร้า
- [ ] ชำระเงิน
- [ ] พิมพ์ใบเสร็จ
**Inventory:**
- [x] หน้ารายการสินค้า
- [ ] เพิ่ม/แก้ไขสินค้า
- [ ] ตัดสต็อกอัตโนมัติ
**Reports:**
- [ ] ยอดขายรายวัน
- [ ] สินค้าขายดี
Progress Tracking Structure
In Memory (.toh/progress.md)
# 📊 Project Progress
## Overview
- Project: ร้านกาแฟ
- Type: F&B
- Started: 2024-12-03
- Last Updated: 2024-12-03 14:30
## Phases
### Phase 1: UI Creation
- Status: ✅ Complete
- Started: 2024-12-03 10:00
- Completed: 2024-12-03 12:00
- Items:
- [x] Dashboard page
- [x] POS page
- [x] Menu management
- [x] Orders page
### Phase 2: Logic Implementation
- Status: ⏳ In Progress
- Started: 2024-12-03 12:30
- Items:
- [x] Product store
- [x] Cart logic
- [ ] Order processing
- [ ] Payment integration
- [ ] Receipt generation
### Phase 3: Database Connection
- Status: ⬚ Not Started
- Items:
- [ ] Supabase setup
- [ ] Tables creation
- [ ] RLS policies
- [ ] API integration
### Phase 4: Testing
- Status: ⬚ Not Started
- Items:
- [ ] Unit tests
- [ ] E2E tests
- [ ] Manual testing
### Phase 5: Deployment
- Status: ⬚ Not Started
- Items:
- [ ] Vercel setup
- [ ] Environment config
- [ ] Domain setup
## Statistics
- Total Items: 20
- Completed: 8
- In Progress: 2
- Remaining: 10
- Completion: 40%
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.
- 2d ago First seen · 379 lines · 57 tokens per session scan A 938b903b7289
progress-tracking is a skill published in the GitHub repository wasintoh/toh-framework (95 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 2,090 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-30.
Other skills, from other repositories
goga-change
Specification-governed maintenance workflow orchestrator.
task-record-contract
Use when creating, updating, or reading the task record for a single implementation task. Covers required task sections, no-placeholder rules, files-first task-file frontmatter, work-unit summary template, implementation artifact linkage, and safe GitHub projection posting practices. Backend projections are documented…
setup-agenticloop
Use when a maintainer or human is setting up Agentic Loop in a target project for the first time, when source document names are non-standard or ambiguous, when .agenticloop/project.md is still unconfirmed, or when a human wants to update its development-stage profile. Discovers bounded candidate project docs once…
new-project
Sidecar skill for the /new-project workflow. Use this skill whenever a new project is initialized, when establishing architecture specs, database schemas, roadmap phases, or local project rules. Even if the user does not explicitly mention "standards" or "design patterns", consult this skill to ensure the project is…
open
Companion skill for the /open workflow. Automates workspace diagnostic steps when starting a new session on a project. Collects active session status, project contracts, active task metrics, compact memory presence, roadmap phases, pending brainstorms, and git status.
estimate-size
Estimate software tickets and work items with a configurable relative-sizing workflow. Respect dedicated estimators and local project rules, and use the built-in defaults when no local rules are provided.