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-046git 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-046)<a href="https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-046"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-046.svg" alt="Measured on agentmods" 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.00034 | $0.00629 |
| Opus 5 | $0.00017 | $0.00315 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
skill-046 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 7d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Contribution Tracker
Monitor and visualize contribution metrics from GitHub repositories.
Usage
gh contribution <command> [flags]
Core Commands
track: Track contributions across repositories
visualize: Generate visual reports of contributions
compare: Compare contributions between team members
export: Export contribution data for analysis
Use gh contribution <command> --help for more information about a command.
gh contribution track
Track contributions across repositories for a specified time period.
USAGE
gh contribution track <repo> [flags]
FLAGS
-R, --repo [HOST/]OWNER/REPO Specify the repository to track contributions
--from DATE Start date for tracking
--to DATE End date for tracking
INHERITED FLAGS
--help Show help for command
EXAMPLES
$ gh contribution track OWNER/REPO --from 2023-01-01 --to 2023-12-31
LEARN MORE
Use 'gh contribution track --help' for more information about this command.
gh contribution visualize
Generate visual reports of contributions.
USAGE
gh contribution visualize <repo> [flags]
FLAGS
-R, --repo [HOST/]OWNER/REPO Specify the repository for visualization
--format FORMAT Specify the output format (png, pdf)
INHERITED FLAGS
--help Show help for command
EXAMPLES
$ gh contribution visualize OWNER/REPO --format png
LEARN MORE
Use 'gh contribution visualize --help' for more information about this command.
gh contribution compare
Compare contributions between team members.
USAGE
gh contribution compare <member1> <member2> [flags]
FLAGS
-R, --repo [HOST/]OWNER/REPO Specify the repository for comparison
INHERITED FLAGS
--help Show help for command
EXAMPLES
$ gh contribution compare memberA memberB -R OWNER/REPO
LEARN MORE
Use 'gh contribution compare --help' for more information about this command.
gh contribution export
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.
- 7d ago First seen · 122 lines · 34 tokens per session scan A 72f18dead2fb
skill-046 is a skill published in the GitHub repository legendtkl/agentic-skill-router (5 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 629 once invoked, about $0.0002 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-08-31.
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…