Borrowing it
Nothing to install: this file belongs to harshanandak/forge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/harshanandak/forge/master/.agents/skills/triage-ready/SKILL.mdgit clone --depth 1 https://github.com/harshanandak/forgeWrote 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/harshanandak/forge/triage-ready)<a href="https://agentmods.dev/skills/harshanandak/forge/triage-ready"><img src="https://agentmods.dev/badge/skills/harshanandak/forge/triage-ready.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.00240 | $0.01546 |
| Opus 5 | $0.00120 | $0.00773 |
| Sonnet 5 | $0.00048 | $0.00309 |
| Haiku 4.5 | $0.00024 | $0.00155 |
Grade A, and why
triage-ready 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage: what should I work on next
A read-only orientation skill. It answers "what is the single best thing to work
on right now, and why?" and hands the pick off to claim-safety / dev — it
never mutates the store itself.
Readiness in the Forge kernel is a derived read model: an issue is ready only when every dependency is satisfied, it is unclaimed (no live lease), it is a claimable type (epics and decisions never enter the queue), and no defer window holds it back. Because it is derived, always recompute it — never trust a cached "status == ready". Recompute means: run the query fresh each time.
Do NOT use board
forge board reads a legacy snapshot store, not the live kernel, so its readiness
can be stale or wrong. This skill uses forge issue ready, forge issue blocked,
and forge issue stats exclusively.
Procedure
1. Take the pulse
forge issue stats --json
Returns data.counts (open/done/cancelled — keys are present only when
non-zero, and there is no in_progress bucket: claimed work stays in status
open and is surfaced via active_claims), ready_count, blocked_count, and
active_claims. A high blocked_count relative to
ready_count is your signal that dependency repair (not new work) is the real
bottleneck — hand off to dependency-planning / backlog-hygiene.
2. Rank the ready queue
forge issue ready --json
data.issues[] comes back ordered by rank (priority ascending, then id), each
carrying id, title, type, priority (P0..P4), rank, blocked,
claimed_by, parent_id, labels[], and dependencies[]. The top item is your
default pick. Surface the top few (see Fork points for how many), not the whole
list.
3. Explain WHY the top item is ready
Do not just name it — justify it. Pull its full record:
forge issue show <id> --json
State the reason in one sentence, drawn from the record:
- Priority / rank —
P0atrank0 outranks everything below it. - Dependencies satisfied — every id in
dependencies[]is closed/done, so nothing gates it (blocked: false). - Unclaimed —
claimed_byisnull, so no other agent holds the lease. - Claimable type — it is a
task/feature/bug, not anepic/decision.
What ships with it
2 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.
- 8d ago First seen · 124 lines · 240 tokens per session scan A ebd7df0bb399
triage-ready is a skill published in the GitHub repository harshanandak/forge (4 stars, last pushed 8d ago), licensed MIT. It adds 240 tokens to every session and 1,546 once invoked, about $0.0012 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.