Borrowing it
Nothing to install: this file belongs to Piyush8296/claude-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Piyush8296/claude-workspace/main/.claude/commands/ticket.mdgit clone --depth 1 https://github.com/Piyush8296/claude-workspaceWrote 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/piyush8296/claude-workspace/ticket)<a href="https://agentmods.dev/commands/piyush8296/claude-workspace/ticket"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/ticket.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.00015 | $0.00515 |
| Opus 5 | $0.00008 | $0.00258 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
ticket 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 6d 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
Ticket Workflow
Work on ticket: $ARGUMENTS
Instructions
1. Understand the ticket
If a ticket tracker MCP is available, fetch ticket details. Otherwise, ask the user to provide:
- Title and description
- Acceptance criteria
- Design links or screenshots
- Dependencies or blockers
Summarize:
- What needs to be done
- Acceptance criteria (as checklist)
- Scope boundaries (what's NOT included)
2. Explore the codebase
Before writing any code:
- Search for related existing components/utilities
- Understand current patterns in the area you'll modify
- Identify files that need changes
- Check for existing tests
3. Create a feature branch
git checkout main && git pull
git checkout -b feat/$ARGUMENTS-<brief-slug>
4. Plan the implementation
Before coding, outline:
- Files to create or modify
- Component hierarchy (if UI work)
- State management approach
- API integration points
- Test strategy
Ask for confirmation before proceeding.
5. Implement with TDD
For each unit of work:
- Write a failing test that captures the requirement
- Implement the minimal code to pass
- Refactor for clarity and patterns
- Commit with descriptive conventional commit message
6. Verify quality
npx tsc --noEmit # Type check
npx eslint src/ # Lint
npx vitest run # Unit tests
npx prettier --check src/ # Format
7. Create PR
git push -u origin HEAD
gh pr create --title "feat($ARGUMENTS): <description>" --body "<generated PR description>"
Link the PR to the ticket if possible.
8. Checklist before marking done
- All acceptance criteria met
- Tests written and passing
- No TypeScript errors
- No lint warnings
- Accessibility verified
- Responsive across breakpoints
- Loading, error, and empty states handled
- PR description complete
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.
- 6d ago First seen · 88 lines · 15 tokens per session scan A 7feaa71ab2a6
ticket is a command published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 515 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
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
resume_handoff
Resume work from handoff document with context analysis and validation.
create_handoff
Create handoff document for transferring work to another session.
update-docs
Scan for recently modified files and update corresponding documentation.
handoff
Create a handoff document for seamless session continuity.