Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gtrabanco/agentic-workflownpx agentmods add skills/gtrabanco/agentic-workflow/unit-laneWrote 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/gtrabanco/agentic-workflow/unit-lane)<a href="https://agentmods.dev/skills/gtrabanco/agentic-workflow/unit-lane"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/unit-lane/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gtrabanco/agentic-workflow/unit-lane"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/unit-lane.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.02055 |
| Opus 5.5 | $0.00021 | $0.00822 |
| Sonnet 5.5 | $0.00011 | $0.00411 |
| Haiku 4.5 | $0.00005 | $0.00205 |
Grade A, and why
unit-lane 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Lane — Adaptive Conductor
One document, adaptive steps. The lane reads a closed catalog, triages which steps a unit needs, executes them in order, and commits at each gate. Replaces: design-feature, plan-feature, review-spec, review-plan.
Turn contract
Tick every box before ending the turn; an unchecked box means the turn is not done:
✓ Triage ran (bun scripts/unit-route.mjs --triage <slug>) and its block pasted
verbatim into the unit doc's Evidence section as the authoritative step list
✓ Unit doc exists at docs/features/<NN>-<slug>/SPEC.md (created from template
if new, with all mandatory sections filled or n/a)
✓ Guard ran (bun scripts/diff-guard.mjs --base <ref>) after each implement step;
on BREACH: re-triage or record exception, never shrink the diff
✓ Unit doc's Evidence rows updated (command → exit/digest → output → verified-by)
and Progress log updated (dated entry) before every commit
✓ → Next: block printed as the absolute last output
When to use
- A known unit slug:
unit-lane <NN-slug> - A raw idea (no slug yet):
unit-lane "<idea description>" - A tracked fix issue (no fix folder yet):
unit-lane --fix <issue-number> - A tracked roadmap feature issue (no feature folder yet):
unit-lane --from-issue <issue-number> - Force re-triage:
unit-lane <NN-slug> --retriage
Both --fix <n> and --from-issue <n> are the exact forms
scripts/unit-route.mjs prints for a tracked issue with no unit folder
(route: plan-from-issue) — never invent a different spelling.
Step 0 — Discover the project
Per the agent guide's Workflow conventions + documentation map, then read
docs/features/_TEMPLATE/SPEC.md (the unit doc template). If the unit folder
exists, read its current SPEC.md to avoid overwriting. If this work returns
to an area other unit docs already touch, scan their ## Future sections and
surface each open row as plan-now / keep-deferred / discard before continuing.
Process
1. Resolve or create the unit doc
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +9 lines 46558ad1b6bf
- 8d ago Changed 1be0716a68d1
- 15d ago Changed 300f31bef558
- 21d ago Changed · +15 lines a9874d62b542
- 23d ago First seen · 154 lines · 53 tokens per session scan A da6855ba0923
unit-lane is a skill published in the GitHub repository gtrabanco/agentic-workflow (22 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,055 once invoked, about $0.0002 per session on Opus 5.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-09-23.
Other skills, from other repositories
curate-collection
Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use…
design-on-call-rotation
Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or…
design-training-program
Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training…
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
conduct-retrospective
Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant…
create-github-issues
Structured GitHub issue creation from review findings or task breakdowns. Groups related findings into logical issues, applies labels, and produces issues with standard templates including summary, findings, and acceptance criteria. Designed to consume output from review-codebase or similar review skills.