Borrowing it
Nothing to install: this file belongs to CynaCons/PowerScroll. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CynaCons/PowerScroll/main/.agents/skills/powerscroll-release/SKILL.mdgit clone --depth 1 https://github.com/CynaCons/PowerScrollWrote 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/cynacons/powerscroll/powerscroll-release)<a href="https://agentmods.dev/skills/cynacons/powerscroll/powerscroll-release"><img src="https://agentmods.dev/badge/skills/cynacons/powerscroll/powerscroll-release/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/cynacons/powerscroll/powerscroll-release"><img src="https://agentmods.dev/badge/skills/cynacons/powerscroll/powerscroll-release.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.00058 | $0.00395 |
| Opus 5.5 | $0.00023 | $0.00158 |
| Sonnet 5.5 | $0.00012 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
powerscroll-release 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.
What it actually says
PowerScroll Release
Use the repository's canonical release documentation rather than reconstructing the process from shell history or prior chat.
- Read
docs/RELEASING.mdcompletely before any version, tag, npm, Registry, GitHub release, or Pages mutation. - Read
docs/DEPLOYMENTS.md, then query every live surface in scope because the ledger may lag production. - Determine whether the change is app-only, build/docs-only, MCP-only, or coordinated. Publish only the surfaces required by that classification.
- Preserve unrelated working-tree changes. Never publish uncommitted or unverified bytes, reuse an immutable version, move a published tag, expose a credential, or bypass a failed check without reporting it.
- Require explicit user authorization immediately before an external publish or tag push unless the current request already clearly grants it. Browser, passkey, or GitHub device authorization remains the user's step.
- For MCP publication, enforce the case-sensitive
io.github.CynaCons/powerscrollidentity and npm-before-Registry order. - After publishing, verify the public APIs and artifacts, update the deployment ledger from observed results, and report partial success honestly if surfaces diverge.
The full Playwright campaign is local pre-tag evidence, not a publishing-job
gate. Follow CLAUDE.md for planning, SRS, showcase, commit, and test-reporting
requirements that are outside distribution mechanics.
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 · 32 lines · 58 tokens per session scan A 2e0f3816396c
powerscroll-release is a skill published in the GitHub repository CynaCons/PowerScroll (0 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 395 once invoked, about $0.0002 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.
powerscroll-release compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| powerscroll-releaseCynaCons/PowerScroll | Skill | 0 | 2d ago | MIT | A | 58 | Claude Code, Codex |
| merge-seedkriasoft/react-starter-kit | Skill | 24k | 5d ago | MIT | A | 49 | Claude Code, Codex |
| release-safetytamagui/tamagui | Skill | 14k | today | MIT | A | 0 | Claude Code |
| anarlogfastrepl/anarlog | Skill | 9.8k | yesterday | MIT | A | 50 | Claude Code |
| open-prf5/unovis | Skill | 2.9k | yesterday | Apache-2.0 | A | 67 | Claude Code, Codex |
| dev-fixHoangNguyen0403/agent-skills-standard | Skill | 583 | yesterday | MIT | A | 43 | Codex |
| triaging-merge-queue-failuresPostHog/posthog | Skill | 41k | yesterday | none | A | 180 | Claude Code, Codex |