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 wenext-limited/playbook-cocos --skill cocos-playbook-syncgit clone --depth 1 https://github.com/wenext-limited/playbook-cocosWrote 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/wenext-limited/playbook-cocos/cocos-playbook-sync)<a href="https://agentmods.dev/skills/wenext-limited/playbook-cocos/cocos-playbook-sync"><img src="https://agentmods.dev/badge/skills/wenext-limited/playbook-cocos/cocos-playbook-sync/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/wenext-limited/playbook-cocos/cocos-playbook-sync"><img src="https://agentmods.dev/badge/skills/wenext-limited/playbook-cocos/cocos-playbook-sync.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.00101 | $0.05363 |
| Opus 5.5 | $0.00040 | $0.02145 |
| Sonnet 5.5 | $0.00020 | $0.01073 |
| Haiku 4.5 | $0.00010 | $0.00536 |
Grade A, and why
cocos-playbook-sync 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 2mo 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 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.
- 2mo ago First seen · 545 lines · 101 tokens per session scan A cbafef3fd997
cocos-playbook-sync is a skill published in the GitHub repository wenext-limited/playbook-cocos (2 stars, last pushed 2mo ago), with no licence file. It adds 101 tokens to every session and 5,363 once invoked, about $0.0004 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-31.
Other skills, from other repositories
code-review-github
GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge.
github
A writing guide for GitHub issues, pull requests, code reviews, and release notes in Zhin projects. GitHub is a service where teams track bugs, discuss changes, review code, and publish project updates.
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
github-repository
A GitHub repository workflow skill for preparing a workspace, applying file patches, pushing a branch, and creating a pull request. A pull request is a proposed code change submitted for review before it is merged.
commit-push-pr
Commit changes, push to remote, and create a pull request. Use for completing features or fixes ready for review.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…