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/shwilliamson/automatasaurus/auto-work-issuegit clone --depth 1 https://github.com/shwilliamson/automatasaurusWrote 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/shwilliamson/automatasaurus/auto-work-issue)<a href="https://agentmods.dev/commands/shwilliamson/automatasaurus/auto-work-issue"><img src="https://agentmods.dev/badge/commands/shwilliamson/automatasaurus/auto-work-issue.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 | $0.00000 | $0.00400 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
auto-work-issue 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 4d 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
Work - Process a Specific Issue
Work on a specific GitHub issue by number.
Workflow Mode
WORKFLOW_MODE: single-issue
AUTO_MERGE: false
IMPORTANT: In single-issue mode, do NOT auto-merge. Notify the user when the PR is ready for their review and merge.
Instructions
Load and follow the work-issue skill with ISSUE_NUMBER = $ARGUMENTS.
1. Load the Skill
Load the work-issue skill which contains the full implementation workflow.
If agent teams are enabled (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in settings), also load the team-coordination skill for team patterns.
2. Execute the Workflow
Follow the work-issue skill steps:
- Get issue details for issue #$ARGUMENTS
- Check dependencies
- Get design specs if UI work
- Implement via developer agent
- Coordinate reviews (Architect, Designer if UI, Tester)
- Handle any change requests
3. Report Result (Do NOT Merge)
When the skill workflow completes with SUCCESS:
gh pr comment {pr_number} --body "**[Product Owner]**
All required reviews complete:
- ✅ Architect
- ✅ Tester
[- ✅ Designer (if applicable)]
PR is ready for merge. Awaiting user action."
Report to user:
PR #{pr_number} is ready for your review and merge.
All approvals received:
- ✅ Architect
- ✅ Tester
Link: {pr_url}
When you're ready, merge the PR to complete issue #$ARGUMENTS.
STOP HERE - Do NOT merge in single-issue mode. The user will merge manually.
Issue Number
$ARGUMENTS
Begin by loading the work-issue skill, then start with Step 1: Get Issue Details.
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.
- 4d ago First seen · 76 lines · 0 tokens per session scan A 54de5daf63de
auto-work-issue is a command published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 400 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-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.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].