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 digital-stoic-org/agent-skills --skill triagegit clone --depth 1 https://github.com/digital-stoic-org/agent-skillsWrote 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/digital-stoic-org/agent-skills/triage)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/triage"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/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/digital-stoic-org/agent-skills/triage"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00000 | $0.01519 |
| Opus 5 | $0.00000 | $0.00759 |
| Sonnet 5 | $0.00000 | $0.00304 |
| Haiku 4.5 | $0.00000 | $0.00152 |
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 5d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTD Triage
Two-pass inline triage. Claude annotates inbox, human reviews in Obsidian, Claude routes on second pass.
Two-Pass Flow
Pass 1: Annotate (no second // on lines)
Trigger: /gtd:triage when ### New has lines WITHOUT //
- Read
/praxis/gtd/01-inbox.md, extract### Newitems - If empty: report "📭 Inbox empty" and stop
- Scan
/praxis/projects/for routing targets (Glob + Grep) - Append
// → target #tagsto each unannotated line - Report: "✏️ Annotated X items. Review in Obsidian, append your
//comments, then run/gtd:triageagain."
Pass 2: Route (lines have two // blocks)
Trigger: /gtd:triage when ### New has lines with TWO // blocks
- Read inbox, parse lines with two
//blocks - If none found: report "⏳ No reviewed items yet" and stop
- For each reviewed line, interpret the second
//:// ok→ route using Claude's proposal (first//)// ok → different-target #tags→ route with human override// delete→ remove from inbox entirely// any other text→ interpret intent (question = flag with ❓, target name = reroute)
- Apply routing to destination project files
- Remove routed + deleted lines from
### New - Leave lines with only one
//(unreviewed) untouched — never strip proposals - Report summary
Auto-detect Pass
On invocation, detect which pass to run:
- If ANY line in
### Newhas two//blocks → Pass 2 - If lines exist without
//→ Pass 1 - If mixed: run Pass 2 first (process reviewed), then Pass 1 on remaining
Project Discovery
Scan /praxis/projects/ for routing targets:
- Glob:
/praxis/projects/**/*.md - Grep: search project content for keyword match
- Use folder name as shorthand (e.g.,
mind-body,slasheo,villa-nara)
Classification
Type: task | reference | waiting-for | someday | trash | project-seed | article | video
Tags: ONLY allowed GTD tags
- Priority:
#next#frog#waiting#recurring - Context:
#phone#field#admin#read-quick#read-deep#read-book#listen#watch#shop - Energy:
#deep#braindead - People:
#agenda/Name#waiting/Name - No tag = backlog
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.
- 5d ago First seen · 154 lines · 0 tokens per session scan A 6d4d0467ce89
triage is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,519 tokens. 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-04.
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.