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 skills/seabbs/skills/bot-tasksnpx skills add seabbs/skills --skill bot-tasksgit clone --depth 1 https://github.com/seabbs/skillsWrote 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/skills/seabbs/skills/bot-tasks)<a href="https://agentmods.dev/skills/seabbs/skills/bot-tasks"><img src="https://agentmods.dev/badge/skills/seabbs/skills/bot-tasks.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.00021 | $0.00784 |
| Opus 5 | $0.00010 | $0.00392 |
| Sonnet 5 | $0.00004 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
bot-tasks 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Bot Task Requests
Check the bot account's GitHub notifications for issues and PRs where the owner has asked the bot to do something, then execute those tasks.
Read the bot and owner accounts from the org's CLAUDE.md ## Automation config table (bot_account and owner_account).
Helper script
A pre-built script at ~/.claude/scripts/bot-tasks.sh collects unprocessed task requests in one pass.
Run it first to avoid spending tokens on notification parsing.
~/.claude/scripts/bot-tasks.sh > /tmp/bot-tasks.json
If the script is missing or not executable, run /setup-scripts to regenerate it.
The script outputs a JSON object with:
notifications: raw notification listtasks: array of unprocessed task requests withthread_id,repo,type,number,title,url,comment_id,request(the comment body)
Tasks are identified by:
- Direct mentions of the bot account in comments by the owner
- Comments by the owner on bot-authored issues/PRs containing task language
- Filtered to exclude comments already reacted to with 👀 (eyes emoji)
Emoji deduplication
When a task request is processed:
- React to the comment with 👀 (eyes) to mark it as seen
- This prevents re-processing on future runs
gh api -X POST "repos/{repo}/issues/comments/{comment_id}/reactions" -f content=eyes
Cron integration
A cron trigger script at ~/.claude/scripts/cron-bot-tasks.sh polls every 5 minutes.
It only triggers Claude Code if there are new unprocessed requests.
Set up via: crontab -e and add:
*/5 * * * * ~/.claude/scripts/cron-bot-tasks.sh >> ~/.claude/logs/cron-bot-tasks.log 2>&1
Phase 1: Parse script output
Read the tasks array from the JSON.
Skip if empty.
Phase 2: Triage
Present a numbered list of tasks found:
- Issue/PR link
- What the owner asked for (quote the relevant comment)
- Repo
- Estimated complexity (simple/medium/complex)
Ask the user to confirm which tasks to execute, or proceed with all if invoked with --all.
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.
- 5d ago First seen · 97 lines · 21 tokens per session scan A 1653a532c86c
bot-tasks is a skill published in the GitHub repository seabbs/skills (5 stars, last pushed 11d ago), licensed MIT. It adds 21 tokens to every session and 784 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…