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.
git clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote 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/commands/boparaiamrit/skills-by-amrit/progress)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/progress"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/progress/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/commands/boparaiamrit/skills-by-amrit/progress"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/progress.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.00014 | $0.00612 |
| Opus 5 | $0.00007 | $0.00306 |
| Sonnet 5 | $0.00003 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
progress 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 8d 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
/progress — Project Progress
Display the current state of the project, including phase completion, task status, and recent activity.
Instructions
Step 1: Load Project State
# Check if .planning exists
ls .planning/ 2>/dev/null
# Load state
cat .planning/STATE.md 2>/dev/null
cat .planning/ROADMAP.md 2>/dev/null
cat .planning/config.json 2>/dev/null
If .planning/ doesn't exist, inform the user:
No project state found. Run
/init-projectto initialize project tracking.
Step 2: Calculate Progress
Parse the state and roadmap to determine:
- Which phase is current
- How many tasks are complete vs. remaining
- What's active right now
- Any blockers
Step 3: Display Progress Dashboard
# 📊 Project Progress: [Name]
## Overall Status: 🟢 On Track / 🟡 At Risk / 🔴 Blocked
### Phase Overview
| Phase | Name | Status | Progress |
|-------|------|--------|----------|
| 1 | [Name] | ✅ Complete | 5/5 tasks |
| 2 | [Name] | 🔄 In Progress | 3/7 tasks |
| 3 | [Name] | ⬜ Not Started | 0/4 tasks |
### Current Phase: Phase [N] — [Name]
**Active tasks:**
- 🔄 Task 3: [title] — in progress
- ⬜ Task 4: [title] — waiting on Task 3
**Completed tasks:**
- ✅ Task 1: [title]
- ✅ Task 2: [title]
**Blocked tasks:**
- 🔴 Task 5: [title] — blocked by [reason]
### Recent Activity
- [timestamp] — Completed Task 2
- [timestamp] — Started Phase 2
- [timestamp] — Verified Phase 1
### Plans
| Plan | Phase | Status | Tasks |
|------|-------|--------|-------|
| [plan-1] | 1 | ✅ | 5/5 |
| [plan-2] | 2 | 🔄 | 3/7 |
### Verification Status
- Phase 1: ✅ Verified
- Phase 2: ⬜ Not yet verified
### Blockers
[None / List of current blockers]
### What's Next
- [Next logical action based on current state]
Step 4: Phase Detail (If Requested)
If $ARGUMENTS contains a phase number, show detailed task-level status for that phase including individual task completion, files modified, and verification status.
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.
- 8d ago First seen · 91 lines · 14 tokens per session scan A a28874cc449b
progress is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 612 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.