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/watt-mind/factory/unblock-digestgit clone --depth 1 https://github.com/watt-mind/factoryWrote 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/agents/watt-mind/factory/unblock-digest)<a href="https://agentmods.dev/agents/watt-mind/factory/unblock-digest"><img src="https://agentmods.dev/badge/agents/watt-mind/factory/unblock-digest.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.00135 |
| Opus 5 | $0.00000 | $0.00068 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
unblock-digest 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.
What it actually says
unblock-digest — closed-registry action
Not a prompt: this definition executes a fixed command template via the
deterministic command adapter (lib/adapters/command.mjs). No model runs.
bun orchestrator/digest.mjs --repo {repo}
Read-only report of every ai:blocked ticket for the repo: the blocking
question, hold age, and ANSWERED markers where a reply already exists. Writes
nothing anywhere — the captured log is the deliverable, and the agent pass
that acts on holds (unblock-scan/unblock-apply) is a separate, watched
route.
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 · 15 lines · 0 tokens per session scan A 551dc3472350
unblock-digest is an agent published in the GitHub repository watt-mind/factory (10 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 135 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 agents, from other repositories
issue-tracker
Issues and PRDs for this repo live as tasks on the dev-3.0 Kanban board, managed through the dev3 CLI (the same board this project ships). There is no separate issue tracker — a task is an issue. External GitHub PRs are pulled in as a secondary triage surface (see below).
triage-labels
The skills speak in terms of five canonical triage roles. On this repo the tracker is the dev-3.0 Kanban board (see docs/agents/issue-tracker.md), so each role is a dev3 label applied to the task. dev3 statuses/columns (todo, in-progress, user-questions, review-by-ai, review-by-user) are managed by hooks and are NOT…
progress
$frontend-delivery NEW/REPLAN -> Brain analysis + stack discovery -> close Brain -> one Orchestrator child (intent=deliver) -> controller-action loop -> jira-call -> Primary Controller -> confirmed result -> same Orchestrator -> dispatch-specialist -> Primary Controller -> specialist -> cleanup/close -> result -> same…
tech-manager
Use to stand up the dev pod, plan sprints, assign work in parallel, run standups, unblock ICs, and track progress. The orchestration layer between executives and ICs. Owns the sprint plan, the kanban board, and the daily report. Spawns parallel dev agents and the code-reviewer; escalates blockers to tech-lead or CTO.
release-manager
Use when the sprint is done and the team wants to prepare a release — assembles a signed, submission-ready build for iOS and Android, owns version bumps, build numbers, release notes, and the submission checklist. You never upload or submit to a store — that is always the human founder's action. Triggered by /app-ship…
product-validator
Use before scope-lock, and again whenever the PRD or the backlog changes materially, to check the derived product documents against the founder's own recorded words. Compares docs/00-founder-intent/ to docs/10-prd.md and flags omitted intent, invented requirements, silent scope change, acceptance criteria that do not…