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 Mr-Salticidae/knowledge-base --skill wechaty-blog-prgit clone --depth 1 https://github.com/Mr-Salticidae/knowledge-baseWrote 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/mr-salticidae/knowledge-base/wechaty-blog-pr)<a href="https://agentmods.dev/skills/mr-salticidae/knowledge-base/wechaty-blog-pr"><img src="https://agentmods.dev/badge/skills/mr-salticidae/knowledge-base/wechaty-blog-pr/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/mr-salticidae/knowledge-base/wechaty-blog-pr"><img src="https://agentmods.dev/badge/skills/mr-salticidae/knowledge-base/wechaty-blog-pr.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.00079 | $0.01025 |
| Opus 5 | $0.00039 | $0.00513 |
| Sonnet 5 | $0.00016 | $0.00205 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
wechaty-blog-pr 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 10d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 10d ago First seen · 141 lines · 79 tokens per session scan A 71a24d68fa7c
wechaty-blog-pr is a skill published in the GitHub repository Mr-Salticidae/knowledge-base (24 stars, last pushed yesterday), with no licence file. It adds 79 tokens to every session and 1,025 once invoked, about $0.0004 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-30.
Other skills, from other repositories
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
conventional-commits-writing
When writing a commit message, branch name or squash title — measure the repo's own convention first, Conventional Commits as fallback — even on a bare 'commit this'.
git-workflow
Use when working with Git — branch naming, commit messages, PR creation, rebasing, or the code review process — even when the user says 'push this' or 'merge the branch' without naming Git.
git-commit
Create well-structured git commits using the Conventional Commits specification. Use when asked to "commit changes", "create a git commit", "stage and commit", "write a commit message", or "/commit". Analyzes diffs to auto-detect type and scope, generates semantic commit messages, and supports intelligent file staging.
GitHub Issue and PR Workflow
List and search issues, PRs, commits; summarize status and reviews.