Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.
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 commands/rohitg00/awesome-claude-code-toolkit/update-statusgit clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkitWrote 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/rohitg00/awesome-claude-code-toolkit/update-status)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/update-status"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/update-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.00000 | $0.00279 |
| Opus 5 | $0.00000 | $0.00139 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
update-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 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.
What it actually says
/update-status - Update Linear Status
Update the status and progress of Linear tickets.
Steps
- Ask the user for the ticket identifier or search by title
- Fetch the current ticket status and details from Linear
- Determine the new status: backlog, todo, in progress, in review, done, cancelled
- Update the ticket status in Linear
- Add a comment explaining the status change and any relevant context
- Update the estimate if the scope has changed
- Link any related PRs or commits to the ticket
- Move sub-tasks to appropriate statuses based on the parent update
- Notify relevant team members if the status change requires their action
- Update the cycle progress if the ticket is in an active cycle
- Check for blocked tickets that may now be unblocked
- Report: ticket ID, previous status, new status, updated fields
Rules
- Always add a comment when changing status to explain why
- Do not skip status transitions (e.g., backlog directly to done)
- Link the PR when moving to "in review" status
- Update sub-task statuses consistently with parent status
- Notify the reviewer when moving to "in review"
- Capture the actual completion time when moving to "done"
- Do not reopen closed tickets; create a new ticket referencing the original
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 · 29 lines · 0 tokens per session scan A 68c4356449a4
update-status is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,593 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 279 tokens. 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-09-03.
Other commands, from other repositories
create-docker-mcp-tunnel
Stand up an Anthropic MCP tunnel locally with Docker Compose so Claude can call a private MCP server (manual-credentials quickstart).
vios-architecture
Explain the VIOS stream-processor and sensor microservice deployment architecture: containers, ingress, RTSP, file-upload, WebRTC, Envoy, SDR, routing, and event flow.
deployment
Basic production deployment setup for FastAPI applications.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.