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 routegit 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/route)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/route"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/route/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/route"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/route.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.01160 |
| Opus 5 | $0.00000 | $0.00580 |
| Sonnet 5 | $0.00000 | $0.00232 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
route 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTD Route
Put a known item directly into a known project. No inbox, no triage.
Instructions
- Parse
$ARGUMENTS:<item> [→] <target> #tags→(or->) separates item from target if present (explicit form)- Shortcut form (no
→): target is the last non-tag token before#tags; item is everything before it. Only accept if that token resolves to a project via Glob (Step 2). If it doesn't resolve, ask the user. - Item: everything before
→/ before target token (may contain URLs) - Target: project folder shorthand (e.g.,
read,35-read,38-mind-body,prax) - Tags:
#tagtokens anywhere in arguments
- Resolve target: Glob
/vaults/gtd-pcm/03-projects/{target}*/01-*.md - If no match: report error + list close matches via Glob
03-projects/*/ - Read target file, find insertion section
- Get today's date (Bash:
date +%Y-%m-%d) - Insert
- [ ] <item> #tags [created:: YYYY-MM-DD]at end of matched section (before next heading) - Report: "✅ Routed to {target}/{section}"
Section Matching
Route by tag to standard project template sections:
| Tag present | Insert into section |
|---|---|
#next or #frog |
### ⚡ Next |
#waiting or #waiting/Name |
### 👥 Waiting For |
| (any other or none) | ### 📋 Backlog |
No fallback. If the expected section is missing, STOP and report:
"⚠️ {target} missing {section} — update project to standard template (see CLAUDE.md § Project Template), then retry."
Implementation
Step 1: Parse arguments.
- Extract all
#tagtokens first (remove from working string). - If
→or->present: split on it → left=item, right=target. - Else (shortcut form): split remaining string into tokens; last token = candidate target, everything before = item. Validate candidate via Step 2 Glob; if no match, STOP and ask user to disambiguate.
Step 2: Glob /vaults/gtd-pcm/03-projects/{target}*/01-*.md
- If multiple matches: use exact prefix match (e.g.,
35matches35-read/) - If zero matches: Glob
03-projects/*/and report closest options
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 · 95 lines · 0 tokens per session scan A b5c87f7c6cf6
route is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,160 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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.