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 jmagly/aiwg --skill nl-routergit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/nl-router)<a href="https://agentmods.dev/skills/jmagly/aiwg/nl-router"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/nl-router/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/jmagly/aiwg/nl-router"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/nl-router.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.03352 |
| Opus 5 | $0.00010 | $0.01676 |
| Sonnet 5 | $0.00004 | $0.00670 |
| Haiku 4.5 | $0.00002 | $0.00335 |
Grade A, and why
nl-router 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 6d 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 — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nl-router
Route natural language requests to appropriate skills and workflows.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "route this" → explicit NL routing request
- "what skill handles [X]" → skill discovery
Purpose
This skill interprets natural language requests and routes them to the appropriate skills or workflows by:
- Parsing user intent from natural language
- Matching to available skills and commands
- Handling ambiguous requests with clarification
- Suggesting relevant actions
- Learning from routing patterns
Behavior
When triggered, this skill:
-
Parses user intent:
- Extract action verbs
- Identify objects/targets
- Detect qualifiers and constraints
- Recognize context from conversation
-
Matches to skills:
- Search skill trigger patterns
- Score match confidence
- Consider context relevance
-
Routes request:
- High confidence: Route directly
- Medium confidence: Confirm with user
- Low confidence: Offer options
- No match: Suggest alternatives
-
Handles follow-ups:
- Track routing context
- Enable corrections
- Learn from feedback
Routing Patterns
SDLC Workflows
sdlc_patterns:
phase_transitions:
patterns:
- "transition to {phase}"
- "move to {phase}"
- "start {phase}"
- "begin {phase}"
- "ready for {phase}"
routes_to: flow-{from}-to-{to}
extract: [from_phase, to_phase]
gate_checks:
patterns:
- "check gate"
- "can we transition"
- "ready for {phase}"
- "validate {gate}"
- "gate check"
routes_to: gate-evaluation
extract: [gate_name, phase]
project_status:
patterns:
- "where are we"
- "what's next"
- "project status"
- "current phase"
- "status update"
routes_to: project-awareness
action: status_report
risk_management:
patterns:
- "update risks"
- "risk review"
- "new risk"
- "mitigate {risk}"
routes_to: risk-cycle
extract: [risk_id, action]
security_review:
patterns:
- "security review"
- "run security"
- "threat model"
- "security scan"
routes_to: security-assessment
extract: [scope]
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.
- 6d ago First seen · 617 lines · 19 tokens per session scan A d18655e4c9ca
nl-router is a skill published in the GitHub repository jmagly/aiwg (210 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 3,352 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-09-03.
Other skills, from other repositories
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
goal-writer
Drafts a goal+rider document pair that briefs an autonomous coding agent on one round of work — a goal file under 4,000 characters (sized to fit the /goal command in both Claude Code and Codex) plus an unbounded rider with phased plans and named depth tests. Use when the user says "draft a goal", "write a goal+rider"…
horizon
Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.
check-in
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
hyperplan
Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.