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/BitYoungjae/marketplaceWrote 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/bityoungjae/marketplace/status)<a href="https://agentmods.dev/commands/bityoungjae/marketplace/status"><img src="https://agentmods.dev/badge/commands/bityoungjae/marketplace/status.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.00020 | $0.00531 |
| Opus 5 | $0.00010 | $0.00266 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
status 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
Project Status Command
Context
- Completed tasks: !
grep -c "\[x\]" task.md 2>/dev/null || echo "0" - Pending tasks: !
grep -c "\[ \]" task.md 2>/dev/null || echo "0" - Plan metadata: !
head -20 plan.md 2>/dev/null || echo "No plan.md found"
Task
Generate a progress report for this learning resource project.
Step 1: Check Prerequisites
If task.md does not exist, report:
Error: task.md not found.
Run /init first to initialize the project.
If plan.md does not exist, report:
Error: plan.md not found.
Run /init first to initialize the project.
Step 2: Extract Project Information
From plan.md, extract:
- Project title (first # heading)
- Target System
- Target Audience
- Total Estimated Pages
Step 3: Calculate Progress by Part
For each Part in task.md:
- Count
[x](completed) items - Count
[ ](pending) items - Calculate percentage
Step 4: Identify Next Tasks
List the first 3-5 uncompleted [ ] items from task.md.
Step 5: Output Format
Use this exact format:
=== Learning Resource Status ===
Topic: {PROJECT_TITLE}
Progress: {COMPLETED}/{TOTAL} sections ({PERCENTAGE}%)
Pages: ~{ESTIMATED_DONE}/{TOTAL_PAGES} estimated
Part 1: {STATUS} ({DONE}/{TOTAL})
Part 2: {STATUS} ({DONE}/{TOTAL})
...
Next tasks:
[ ] {SECTION_NUMBER} {SECTION_TITLE} ({PAGES}p)
[ ] {SECTION_NUMBER} {SECTION_TITLE} ({PAGES}p)
[ ] {SECTION_NUMBER} {SECTION_TITLE} ({PAGES}p)
Status labels:
- "Complete" if all items done
- "In Progress" if some items done
- "Pending" if no items done
Notes
- Page estimation: assume completed sections contribute their planned pages
- If Part structure is unclear, group by Chapter instead
- Keep output concise and scannable
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 · 83 lines · 20 tokens per session scan A 9cda834c4d99
status is a command published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 531 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.