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 skills add aldianriski/lean-flow --skill triagegit clone --depth 1 https://github.com/aldianriski/lean-flowWrote 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/aldianriski/lean-flow/triage)<a href="https://agentmods.dev/skills/aldianriski/lean-flow/triage"><img src="https://agentmods.dev/badge/skills/aldianriski/lean-flow/triage.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.1 | $0.00091 | $0.01595 |
| Opus 5 | $0.00046 | $0.00797 |
| Sonnet 5 | $0.00018 | $0.00319 |
| Haiku 4.5 | $0.00009 | $0.00160 |
Grade A, and why
triage 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 8d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
triage
Groom the existing backlog: re-rank, flag, state, and route. Backlog only — never re-orders a
locked Active Sprint. Re-prioritisation and state changes are HITL: propose with reasons, get a
y, then apply.
Pipeline: /task-decomposer (intake) → /triage (groom + re-prioritise) → /lean-doc-generator promote (form sprint) → /orchestrator (build).
When to invoke
- The backlog has grown and priorities have drifted from reality.
- Before a Sprint Promote, to surface what is genuinely ready.
- A specific task needs a state or priority decision.
- A bug report (
BUG.md.template-shaped) needs intake routing.
Task states (light)
A Backlog task carries an optional state: — orthogonal to the HITL/AFK label (which says who
acts, not whether it's ready):
| state | meaning |
|---|---|
ready |
fully specified, has a done-when — promotable |
needs-info |
missing detail or an unanswered question — not promotable yet |
blocked |
waiting on a dependency or another task (depends-on) |
Rejected work is not a state — it leaves the backlog (see .out-of-scope/). Default when unset:
ready if it has a done-when, else needs-info.
Flow
- Scan
.out-of-scope/first — if a backlog task resembles a prior rejection, surface it and ask before keeping it. - Load — read
TODO.md§ Backlog (+ rootTECH-DEBT.md; legacy: TODO § Tech Debt). Ignore the Active Sprint. - Bug intake — a BUG.md-shaped item (or bug-flavored backlog entry) is routed, not ranked like a feature:
- known cause + trivial fix → convert to
TASK-NNN(state: ready,origin: triage-bug) - unknown cause / needs investigation → record as a task,
next: /diagnose(origin: triage-bug) - systemic / architectural → file as
TD-NNNin rootTECH-DEBT.md - stamp
origin:on every task you file here — a bug converted at triage never met the intake grill, and the stamp is what stops G1 fast-pathing it on the strength of looking well-formed - then the report itself is done. A
BUG-<slug>.mdis temp-dir intake scaffolding, never a committed doc (STANDARD §2): once its repro and verdict live in the destination, the file has no durable home to be moved to. Carry anything still load-bearing — repro steps especially — into theTASK/TD//diagnosebrief rather than pointing back at a file that will vanish.
- known cause + trivial fix → convert to
- Re-rank — re-evaluate each task's P0–P3 tier; propose moves with a one-line reason each. Order within a tier by dependency, then impact × urgency.
- Flag — surface stale (no movement / superseded), duplicate (same concern → merge or differentiate), conflict (acceptance criteria that contradict another task).
- State — set
ready/needs-info/blocked; forneeds-infolist the specific questions; forblockedname the blocker. - Route rejects — for work that will not be done, write an
.out-of-scope/entry, then remove the task from the backlog with a pointer. - Output — the groomed backlog + a ready-to-promote shortlist (P-order,
readyonly). Apply changes only after humany.
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.
- 8d ago First seen · 92 lines · 91 tokens per session scan A 3cf96394e980
triage is a skill published in the GitHub repository aldianriski/lean-flow (5 stars, last pushed 9d ago), licensed MIT. It adds 91 tokens to every session and 1,595 once invoked, about $0.0005 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.