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/mdsakalu/agent-pluginsWrote 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/mdsakalu/agent-plugins/status)<a href="https://agentmods.dev/commands/mdsakalu/agent-plugins/status"><img src="https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/status/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/mdsakalu/agent-plugins/status"><img src="https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/status.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.00006 | $0.00550 |
| Opus 5.5 | $0.00002 | $0.00220 |
| Sonnet 5.5 | $0.00001 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
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 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
Show detailed status for a workspace.
Resolve the metarepo path by reading ~/.claude/workspace-config.json and expanding ~ to $HOME.
The user's request: $ARGUMENTS
Steps
- Read
~/.claude/workspace-config.jsonto get the metarepo path. Expand~to$HOME. - Determine which workspace to report on:
- If the user specified
<repo>/<workspace>, use it directly - If just
<workspace>, search across all repos - If no argument, try to infer from cwd: check if cwd matches
*/repos/<repo>/<workspace>*and extract both - If unable to determine, list available workspaces and ask
- If the user specified
- Read workspace metadata from
<metarepo>/notes/<repo>/<workspace>/workspace.json:- Show: repo, name, type, purpose, owner, created date, retired status
- Show all references from workspace.json:
- For PRs: show number, URL, JJ change_id, branch
- Optionally get live PR status:
gh pr view <number> --json state,title --repo <github_owner>/<github_repo> - For Jira tickets: show ticket key
- Read notes summary from
<metarepo>/notes/<repo>/<workspace>/README.md(first ~10 lines). - List other files in the notes directory.
- If the workspace directory exists at
<metarepo>/repos/<repo>/<workspace>/, run from it:jj log --limit 5 jj status - Read
.repo.jsonfrom<metarepo>/repos/<repo>/for GitHub owner/repo info (used for PR lookups). - Present all information in a well-organized format.
Important
- Always resolve metarepo from
~/.claude/workspace-config.json, never hardcode paths. - Workspace metadata is in
notes/<repo>/<workspace>/workspace.json(source of truth). - Workspace code lives at
repos/<repo>/<workspace>/. - Handle missing workspaces gracefully — if the directory is gone but notes exist, show available metadata.
- If jj commands fail, report the error but still show metadata from workspace.json.
- Read
.repo.jsonfor GitHub owner/repo to use withgh pr view.
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 · 44 lines · 6 tokens per session scan A 69294558e9ba
status is a command published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 4mo ago), licensed MIT. It adds 6 tokens to every session and 550 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
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.