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 hereinthehive/gotrino-assistant --skill triagegit clone --depth 1 https://github.com/hereinthehive/gotrino-assistantWrote 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/hereinthehive/gotrino-assistant/triage)<a href="https://agentmods.dev/skills/hereinthehive/gotrino-assistant/triage"><img src="https://agentmods.dev/badge/skills/hereinthehive/gotrino-assistant/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/hereinthehive/gotrino-assistant/triage"><img src="https://agentmods.dev/badge/skills/hereinthehive/gotrino-assistant/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.00018 | $0.01744 |
| Opus 5 | $0.00009 | $0.00872 |
| Sonnet 5 | $0.00004 | $0.00349 |
| Haiku 4.5 | $0.00002 | $0.00174 |
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 9d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
Assess an incoming request to determine whether it needs a response and, if so, the size, nature, and priority of that response.
Triage applies to all incoming work — new feature requests, bug reports, internal needs, and technical debt. These are not the same and should not be prioritised the same way. This process provides a shared framework for making that distinction.
Config Integration
Before starting, follow the migration preflight in references/config-migration.md, then read .assistant-config.md from the project root.
If it exists, read the Task Management section to determine:
- Tracker: Where issues are managed (e.g. Linear, GitHub Issues, Jira)
- Accessible via tools: Whether you can create/search issues directly
- Local tasks: Where code-adjacent task files go
If the config doesn't exist or has no task management section, ask the user where they track work before routing (Step 5). Suggest running /teach-charter to set this up permanently.
When to invoke
- A new request or bug arrives (from an issue tracker, chat, or conversation)
- Before starting work on something that hasn't been assessed
- When reprioritising existing work against new information
Step 1: Classify the request
Ask the user (or determine from context) what type of work this is:
| Type | Description |
|---|---|
| Bug | Something that worked before and is now broken |
| Feature | A new capability that doesn't exist yet |
| Enhancement | Improvement to something that already works |
| Debt | Internal cleanup, refactoring, or infrastructure |
If unclear, ask: "Is this fixing something broken, adding something new, improving something existing, or cleaning something up?"
Step 2: Check for duplicates
Before going further, check whether this already exists:
- If the project's tracker is accessible via tools (per config), search it for matching items
- Search the codebase for TODO/FIXME comments related to the issue
- Check the local task location (per config) for related task files
- If a duplicate exists, report it and ask whether to update the existing item or proceed as new
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.
- 9d ago First seen · 193 lines · 18 tokens per session scan A 94c611348ce0
triage is a skill published in the GitHub repository hereinthehive/gotrino-assistant (5 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 1,744 once invoked, about $0.0001 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.
remove
Remove a deployed framework or addon from the current workspace.