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 ALTEN-group/coding-pal --skill triagegit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/triage)<a href="https://agentmods.dev/skills/alten-group/coding-pal/triage"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/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/alten-group/coding-pal/triage"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/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.00081 | $0.00733 |
| Opus 5.5 | $0.00032 | $0.00293 |
| Sonnet 5.5 | $0.00016 | $0.00147 |
| Haiku 4.5 | $0.00008 | $0.00073 |
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 4d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
Produce deterministic triage.md artifacts that a Product Owner can validate quickly and the Think phase can consume without re-discovery. AI enriches, scores, and proposes; the Product Owner decides.
When to Use This Skill
- A candidate need (meeting pack item, support-ticket cluster, audit finding, Learn signal, field note) must become a backlog issue with evidence, a scorecard, and a proposed decision.
- CI must gate a
triage.mdbefore it is attached to an issue, or after the Product Owner has set the decision. - The weekly Triage review needs a deterministic ranking of scored backlog issues.
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/triage/ or .claude/skills/triage/, use that base path.
Workflow
- Read
references/triage-contract.mdnow. It is the authoritative source for headings, fields, scales, decision rules, ledger format, and weights. Scope exploration and scoring judgement are owned by the callingTriage Analystagent, planning session, or issue trigger. - Draft
triage.mdfrom the candidate need and its real evidence. Never invent or paraphrase a client quote. - Validate with the deterministic script from this skill's directory:
# AI output gate: Final (PO) must still be Pending
node scripts/validate-triage.mjs --triage specs/issue-42/triage.md --stage proposed \
--source meetings/2026-09-24-acme-discovery/transcript.md --ledger specs/triage/ledger.md
# Exit gate after the Product Owner has decided
node scripts/validate-triage.mjs --dir specs/issue-42 --stage final
Treat a nonzero validator exit as invalid output and fix the file rather than ignoring errors. Model compliance is advisory; the script is the enforcement gate.
- For the weekly review, rank the backlog deterministically:
node scripts/rank-backlog.mjs --dir specs --weights specs/triage/weights.json
What ships with it
6 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.
- 4d ago First seen · 54 lines · 81 tokens per session scan A b608f3276067
triage is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 81 tokens to every session and 733 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.