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-146git 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-146)<a href="https://agentmods.dev/skills/legendtkl/agentic-skill-router/skill-146"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-146/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-146"><img src="https://agentmods.dev/badge/skills/legendtkl/agentic-skill-router/skill-146.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.00040 | $0.00832 |
| Opus 5 | $0.00020 | $0.00416 |
| Sonnet 5 | $0.00008 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
skill-146 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 8d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Analytics
Leverage GitHub's issue tracking data to get actionable insights.
Usage
gh-issue-analytics <command> [flags]
Core Commands
stats: Generate statistics about issues
trends: Visualize trends in issue creation and resolution
report: Create comprehensive issue reports
export: Export issue data to CSV or JSON
compare: Compare issue metrics between repositories
Use gh-issue-analytics <command> --help for more information about a command.
gh-issue-analytics stats
Generate statistics about issues in a repository.
USAGE
gh-issue-analytics stats <flags>
FLAGS
-R, --repo [HOST/]OWNER/REPO Specify the repository to analyze
INHERITED FLAGS
--help Show help for command
EXAMPLES
$ gh-issue-analytics stats -R OWNER/REPO
$ gh-issue-analytics stats --repo=my-repo
LEARN MORE
Use 'gh-issue-analytics stats --help' for more information about this command.
gh-issue-analytics trends
Visualize trends in issue creation and resolution.
USAGE
gh-issue-analytics trends <flags>
FLAGS
-R, --repo [HOST/]OWNER/REPO Specify the repository to analyze
--from DATE Start date for analysis
--to DATE End date for analysis
INHERITED FLAGS
--help Show help for command
EXAMPLES
$ gh-issue-analytics trends -R OWNER/REPO --from 2023-01-01 --to 2023-12-31
LEARN MORE
Use 'gh-issue-analytics trends --help' for more information about this command.
gh-issue-analytics report
Create comprehensive reports based on issue data.
USAGE
gh-issue-analytics report <flags>
FLAGS
-R, --repo [HOST/]OWNER/REPO Specify the repository for the report
--format FORMAT Specify output format (pdf, html)
INHERITED FLAGS
--help Show help for command
EXAMPLES
$ gh-issue-analytics report --format pdf -R OWNER/REPO
LEARN MORE
Use 'gh-issue-analytics report --help' for more information about this command.
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.
- 8d ago First seen · 147 lines · 40 tokens per session scan A 4b87d97aff20
skill-146 is a skill published in the GitHub repository legendtkl/agentic-skill-router (5 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 832 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.