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 AgiFlow/ai-plugin --skill triagegit clone --depth 1 https://github.com/AgiFlow/ai-pluginWrote 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/agiflow/ai-plugin/triage)<a href="https://agentmods.dev/skills/agiflow/ai-plugin/triage"><img src="https://agentmods.dev/badge/skills/agiflow/ai-plugin/triage/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/agiflow/ai-plugin/triage"><img src="https://agentmods.dev/badge/skills/agiflow/ai-plugin/triage.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.00049 | $0.00404 |
| Opus 5.5 | $0.00020 | $0.00162 |
| Sonnet 5.5 | $0.00010 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00040 |
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 1mo 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.
This is a copy
100% identical to triage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Agiflow Triage
Diagnose before prescribing. Read the workspace first and separate evidence from inference.
Workflow
- Call
get_current_scopeand resolve the target project when one is specified. - Call
list_active_tasks_by_org,list_work_units, andlist_members. - For relevant items, call
get_task,get_work_unit,get_work_unit_progress, andlist_task_commentsto inspect details and documented blockers. - Identify:
- Stalled tasks or work units
- Explicit blockers and unresolved dependencies
- Missing or vague acceptance criteria
- High-priority unassigned work
- Excessive work in progress
- Obsolete or duplicate tasks
- Priority inversions
- Classify each finding as Blocker, Warning, or Note.
- Recommend one specific action for each finding and explain the expected impact.
- Present the report and ask which actions the user approves.
- Execute only approved actions with the appropriate tools, such as
update_task,create_task,batch_create_tasks, orcreate_task_comment. - Re-read affected records to verify the result.
Mutation Rules
- Do not change anything during diagnosis.
- Document the reason with
create_task_commentbefore cancelling or materially re-scoping a task. - Use
update_taskonly after approval for reassignment, priority, status, or scope changes. - Create new tasks only when the user approves the proposed corrective work.
- Do not use deletion as a default cleanup action.
Response
Provide a concise health summary, evidence for each finding, severity, recommended action, and the three highest-priority next steps.
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.
- 1mo ago First seen · 40 lines · 49 tokens per session scan A f770de0be9c6
triage is a skill published in the GitHub repository AgiFlow/ai-plugin (4 stars, last pushed 17d ago), licensed MIT. It adds 49 tokens to every session and 404 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to triage, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.