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 instructions/stackbilt-dev/cc-taskrunner/claude-mdgit clone --depth 1 https://github.com/Stackbilt-dev/cc-taskrunnerWhat 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.00545 | $0.00545 |
| Opus 5 | $0.00272 | $0.00272 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
cc-taskrunner CLAUDE.md 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 yesterday.
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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-taskrunner
Autonomous task queue for Claude Code with safety hooks, branch isolation, and PR creation.
Commands
./taskrunner.sh— Run until queue empty./taskrunner.sh --max N— Run at most N tasks./taskrunner.sh --loop— Loop forever (poll every 60s)./taskrunner.sh --dry-run— Preview without executing./taskrunner.sh add "title"— Add a task to the queue./taskrunner.sh pull --fix-id <uuid>— Pull a QUEUED fix from CodeBeast D1 into queue.json./taskrunner.sh pull --fix-id <uuid> --dry-run— Preview D1 row without writing anything
Key env vars
CC_TASK_TIMEOUT— Watchdog timeout in seconds (default 1500 / 25 min); tasks exceeding this are marked TASK_BLOCKEDCLOUDFLARE_API_TOKEN/CF_ACCOUNT_ID/D1_FIX_QUEUE_DB_ID— Required forpullsubcommand
Structure
taskrunner.sh— Main script (~1150 lines bash + embedded python)hooks/— Safety hook scripts (block-interactive, safety-gate, syntax-check)queue.json— Task queue file (JSON array, gitignored; see queue.example.json)repo-aliases.conf— Repo alias mappings (gitignored; see repo-aliases.example.conf)scripts/— Helper scripts (deploy, pull-fix.sh, cleanup-branches.sh)plugin/— Plugin system (agents, commands, safety)
Conventions
- Bash 4+, Python 3 for JSON manipulation
- All paths relative to script directory
- Tasks use JSON format with id, title, repo, prompt, status fields
- Completion signal: TASK_COMPLETE or TASK_BLOCKED
OSS Policy
This is a public infrastructure package governed by the Stackbilt OSS Infrastructure Package Update Policy.
Rules:
- Additive only — never remove or rename public API without a major version bump
- No product logic — framework patterns and generic utilities only. If a competitor could reconstruct Stackbilt product architecture from this code, it doesn't belong here.
- Strict semver — patch for fixes, minor for new features, major for breaking changes
- Tests travel with code — every public export must have test coverage
- Validate at boundaries — all external API responses validated before returning to consumers
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.
- yesterday First seen · 42 lines · 545 tokens per session scan A da8dd971845d
cc-taskrunner CLAUDE.md is an instructions file published in the GitHub repository Stackbilt-dev/cc-taskrunner (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 545 tokens to every session, about $0.0027 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 instructions, from other repositories
CORE CLAUDE.md
Instructions for DariuszNewecki/CORE, covering claude.md — core, what core is, and what you are, source layout, how to work in this repo and governed and prohibited surfaces.
Specflow CLAUDE.md
Instructions for Hulupeep/Specflow, covering claude.md, project context, specflow rules, rule 1: no ticket = no code and rule 2: commits must reference an issue.
nio CLAUDE.md
Instructions for core0-io/nio, covering nio, skill, project structure, build and release.
agent-fleet-o CLAUDE.md
Claude Code instructions for escapeboy/agent-fleet-o, covering fleetq - community edition, stack, git branching strategy, project structure and routes.
initrunner CLAUDE.md
Instructions for vladkesler/initrunner, covering initrunner and project map.
TitanClip AGENTS.md
AGENTS.md instructions for CES-Ltd/TitanClip, covering titanclip — agent context (repository), quick facts and do not conflate.