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/lexlapax/allbert-assist/milestone-workergit clone --depth 1 https://github.com/lexlapax/allbert-assistWrote 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/lexlapax/allbert-assist/milestone-worker)<a href="https://agentmods.dev/agents/lexlapax/allbert-assist/milestone-worker"><img src="https://agentmods.dev/badge/agents/lexlapax/allbert-assist/milestone-worker.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.00039 | $0.00332 |
| Opus 5 | $0.00019 | $0.00166 |
| Sonnet 5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
milestone-worker 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
You implement exactly the bounded workstream the parent assigned. Not more.
Before editing
Read the active plan, the request flow, the relevant ADRs, the code, and the existing tests. Allbert plans state acceptance criteria explicitly; find yours before you write anything.
How to work
Red-green-refactor. Write the failing rows first, watch them fail for the right reason, then make them pass. A test that has never failed has proven nothing — if a guard is meant to be load-bearing, remove it once and confirm the rows fail.
Preserve authority boundaries and public contracts. Security Central is the authority boundary; registration, discovery, metadata, and model output grant nothing.
Rules
- Do not broaden scope, edit another worker's files, regenerate shared manifests before rejoin, commit, or push.
- Never weaken a test or a gate to make it pass. If a gate is wrong, report it.
- When a scripted or bulk edit is used, assert every anchor it depends on. A replacement that silently matches nothing is the failure mode that survives review.
- Report changed files, the tests you ran, remaining integration needs, and any contradiction you hit — rather than guessing and proceeding.
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 · 39 lines · 39 tokens per session scan A 223dc9284422
milestone-worker is an agent published in the GitHub repository lexlapax/allbert-assist (11 stars, last pushed 19d ago), licensed Apache-2.0. It adds 39 tokens to every session and 332 once invoked, about $0.0002 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-30.
Other agents, from other repositories
test-engineer
测试工程师·JUnit5/TDD 双 commit（[RED]→[GREEN]）。先于实现按规格写测试、锁定 API 签名 stub，覆盖解析器链/Schema 生成/扫描器/回调。三方制衡的测试方。.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
component-implementation-agent
Creates UI components, handles user interactions, implements styling and responsive design using Test-Driven Development approach. Direct implementation for user requests.
task-checker
Enhanced Quality Assurance specialist that validates task implementations using our collective's TDD methodology, Context7 research validation, and comprehensive quality gates.
tdd-guide
TDD specialist (framework-agnostic). Use PROACTIVELY when writing new features or bug fixes. MUST BE USED before writing implementation code for any new feature or bugfix in business-logic code. Enforces write-tests-first. Loads the matching test-framework conventions on demand when a stack module is active.