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.
git clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/commands/fakoli/fakoli-plugins/triage)<a href="https://agentmods.dev/commands/fakoli/fakoli-plugins/triage"><img src="https://agentmods.dev/badge/commands/fakoli/fakoli-plugins/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/commands/fakoli/fakoli-plugins/triage"><img src="https://agentmods.dev/badge/commands/fakoli/fakoli-plugins/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.00005 | $0.00178 |
| Opus 5.5 | $0.00002 | $0.00071 |
| Sonnet 5.5 | $0.00001 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
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.
What it actually says
/triage
Show an unread email inbox summary using the gws CLI.
Instructions
-
If the user provides a query argument, use it as the
--queryflag. Otherwise, show all unread. -
Run the triage command:
gws gmail +triage --format tableOr with a query:
gws gmail +triage --query '<QUERY>' --format table -
Present the results showing sender, subject, and date.
-
If there are many results, suggest using
--max Nto limit. -
Offer to read specific messages or reply if the user wants to take action on any email.
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 · 29 lines · 5 tokens per session scan A aef068efcad1
triage is a command published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 5 tokens to every session and 178 once invoked, about $0.0000 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-03.
Other commands, from other repositories
psalm
Command "psalm" from Marcel-Bich/marcel-bich-claude-marketplace, covering credo - the preacher's guide, step 0: run setup (recommended), entry point, credo's own teachings and topic: the credo workflow (end to end).
versioning
Universal version file discovery and sync. Works with any project structure.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
update
You are executing the /import:update command. Re-fetch documentation from original sources.
spawn
You are executing the /hydra:spawn command. Start an agent in an existing worktree.
explain
Explain the subject in depth using the fixed four-part structure: What, Why, Example, Consequences. Treat the subject as the thing to be explained, not as a literal question.