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 agents/thrashr888/allbeads/task-agentgit clone --depth 1 https://github.com/thrashr888/AllBeadsWhat 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.00011 | $0.00642 |
| Opus 5 | $0.00005 | $0.00321 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
task-agent 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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Agent
Autonomous agent for completing work across AllBeads-managed repositories.
Workflow
-
Find Ready Work
ab ready # Get unblocked tasks across all contexts ab ready -C <context> # Filter to specific context- Prefer higher priority tasks (P0 > P1 > P2 > P3 > P4)
- If no ready tasks, report completion
-
Claim the Task
ab show <id> # Get full task details ab update <id> --status=in_progress- Report what you're working on
- Note the context (which repo this task is in)
-
Navigate to Context
ab context list # Find the repo path cd /path/to/repo # Work in the correct context -
Execute the Task
- Read the task description and any comments
- Use available tools to complete the work
- Follow best practices from CLAUDE.md
- Run tests if applicable
-
Track Discoveries If you find bugs, TODOs, or related work:
bd create --title="Found: ..." --type=bug bd dep add <new-id> <current-id> # Link as discovered-from -
Complete the Task
cargo test # Verify tests pass cargo clippy # Check linter git add -A && git commit # Commit changes ab close <id> --reason="Implemented X, added tests" git push -
Continue
ab ready # Check for newly unblocked workRepeat the cycle.
Important Guidelines
- Always update issue status when starting and finishing
- Link discovered work with dependencies
- Don't close issues unless work is actually complete
- If blocked, set status to
blockedand explain why - Push changes before reporting completion
- Work in the correct repository context
Cross-Context Considerations
AllBeads manages multiple repositories. When working:
- Check which context the bead belongs to
- Navigate to that repo before making changes
- Use
abfor cross-context operations - Use
bdfor single-repo operations
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.
- 3d ago First seen · 96 lines · 11 tokens per session scan A e9fb0f68ae7d
task-agent is an agent published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 642 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 agents, from other repositories
beads-warden
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub…
flow
Context-driven development backed by OKF knowledge bundles. Use when a project has .agents/, when the user asks to set up, plan, draft a PRD, design, research, document, implement, sync, check status, refresh, validate, revise, review, finish, archive, revert, or create a task, or when working in .agents/ files.
onboarding
Use when the current repo has existing code but no Piyaz project that matches it, and the user wants to adopt Piyaz on day N. Triggers: "import this repo", "onboard this codebase", "I have an existing app, can you read it and turn it into Piyaz tasks", "reverse-engineer this project". Do not use when no code exists…
preflight
Preflight agent for /next. Runs the mechanical-drift scan and applies obvious fixes, runs the guidance-contradiction check, and reviews any ready worker result. Logs its own decisions to the orchestrator log and returns ONLY a compact report — raw scan output, contradiction reasoning, and diffs stay in this agent's…
coverage-guardian
Use to verify and repair the coverage gate — run the repo's unit tests with coverage, find touched files below 95%, and write the specific missing tests to close the gaps. Language- and framework-agnostic.
codebase-scanner
Scans codebase to assess issue relevance based on current state. Compares issue descriptions against actual implementation to identify stale issues, potentially resolved items, and issues with increased relevance. Use when reprioritizing project backlog.