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 LSTM-Kirigaya/jinhui-skills --skill port-managergit clone --depth 1 https://github.com/LSTM-Kirigaya/jinhui-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/lstm-kirigaya/jinhui-skills/port-manager)<a href="https://agentmods.dev/skills/lstm-kirigaya/jinhui-skills/port-manager"><img src="https://agentmods.dev/badge/skills/lstm-kirigaya/jinhui-skills/port-manager/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/lstm-kirigaya/jinhui-skills/port-manager"><img src="https://agentmods.dev/badge/skills/lstm-kirigaya/jinhui-skills/port-manager.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.00154 | $0.01017 |
| Opus 5.5 | $0.00062 | $0.00407 |
| Sonnet 5.5 | $0.00031 | $0.00203 |
| Haiku 4.5 | $0.00015 | $0.00102 |
Grade A, and why
port-manager 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 108 lines · 154 tokens per session scan A fd631e084e89
port-manager is a skill published in the GitHub repository LSTM-Kirigaya/jinhui-skills (24 stars, last pushed 2mo ago), with no licence file. It adds 154 tokens to every session and 1,017 once invoked, about $0.0006 per session on Opus 5.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-30.
Other skills, from other repositories
ask-copilot
Use GitHub Copilot CLI in non-interactive mode to ask questions, review code, or generate snippets without manual interaction.
pdd-setup
Set up a repo for PDD. Use when the person asks to set up PDD, add PDD to a project, or connect the PDD skills to this repo. Adds one short PDD block to CLAUDE.md or AGENTS.md.
pdd-bug
PDD bug workflow. Use when the person reports a bug, an error or a wrong result in a PDD project. Reproduce it, fix the prompt and tests (PR 1), then the code (PR 2) if asked.
pdd-feature
PDD feature workflow. Use when the person asks for a new feature or new behavior in a PDD project. Write the prompt, Story and tests (PR 1), then the code (PR 2) if asked.
pdd-prompting
The PDD Prompting guide. Use when you write, change or review a module prompt (.prompt.md), a Story or test cases, or when the person asks how to write prompts in PDD. In PDD, prompts are the source and code follows them.
pdd-small-change
PDD small-change workflow. Use when the person asks for a small, contained change that is easy to undo, such as a typo, a config value or a small fix. Plan it, make it, verify it, one PR.