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 legendtkl/agentic-skill-router --skill skill-069git clone --depth 1 https://github.com/legendtkl/agentic-skill-routerWrote 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/legendtkl/agentic-skill-router/skill-069)<a href="https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-069"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-069/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/legendtkl/agentic-skill-router/skill-069"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-069.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.00028 | $0.01662 |
| Opus 5 | $0.00014 | $0.00831 |
| Sonnet 5 | $0.00006 | $0.00332 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
skill-069 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Description Template Skill
This skill provides everything needed to write high-quality PR descriptions: templates, format specifications, and examples.
Quick Reference
| Command | Description |
|---|---|
/pr-description-template |
Show available templates and help |
/pr-description-template feature |
Example PR for new feature implementations |
/pr-description-template bugfix |
Example PR for bug fixes |
/pr-description-template refactor |
Example PR for refactoring/architectural changes |
/pr-description-template format |
Show complete PR description format |
Available Templates
| Template | Use For | Characteristics |
|---|---|---|
| feature | New functionality, APIs, components | Emphasizes scope, design decisions, future work |
| bugfix | Bug fixes, regressions, hotfixes | Emphasizes root cause, testing, before/after |
| refactor | Architectural changes, code restructuring | Emphasizes compatibility, migration, incremental changes |
Template Selection Guide
Choose feature when:
- Adding new functionality (greenfield development)
- Implementing new APIs, services, or components
- Adding new user-facing features
- Introducing new capabilities to the codebase
Choose bugfix when:
- Fixing a bug of any size
- Addressing regressions
- Hotfixes for production issues
- Correcting unexpected behavior
Choose refactor when:
- Making architectural changes
- Restructuring code without changing behavior
- Reorganizing modules or file structure
- Implementing breaking changes with migration
- Improving code quality without adding features
PR Description Format
Every PR description MUST follow this structure. This is the canonical format for all pull requests.
Required Sections
## Summary
<High-level summary of changes and context for why the changes were made.
Should answer: What does this PR do? Why is it needed?
Keep to 2-4 sentences. Focus on business value and user impact.>
## What's Included
<Compact list organized by category to help reviewer understand scope at a glance>
**Source Code:**
- `path/to/file.py` - Brief description of change
**Tests:**
- `tests/test_file.py` - What's being tested
**Documentation:**
- `docs/file.md` - What was documented (or note if missing)
**Configuration:**
- `pyproject.toml` - Dependencies added/changed
## Key Design Decisions
<Design decisions to document for reviewer context.
Focus on "why this approach" not implementation details.
Number each decision for easy reference in review comments.>
1. **Decision Title**: Rationale for why this approach was chosen over alternatives
2. **Convention Deviation** (if any): Any intentional deviations from development-conventions with justification
## Critical Areas for Review
<Prioritized areas deserving careful review.
Help reviewer focus their attention on what matters most.
Include line numbers when specific ranges need attention.>
1. **`path/to/critical/file.py:L10-L50`** - Description of why this needs careful review (e.g., complex logic, security implications, breaking change)
2. **`path/to/another/file.py`** - Why this is important to review
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 · 251 lines · 28 tokens per session scan A 614d9091a2df
skill-069 is a skill published in the GitHub repository legendtkl/agentic-skill-router (5 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,662 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…