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 agentmods add skills/anyproto/anytype-ts/release-notesnpx skills add anyproto/anytype-ts --skill release-notesgit clone --depth 1 https://github.com/anyproto/anytype-tsWhat 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 | $0.00018 | $0.05424 |
| Opus 5 | $0.00009 | $0.02712 |
| Sonnet 5 | $0.00004 | $0.01085 |
| Haiku 4.5 | $0.00002 | $0.00542 |
Grade C, and why
release-notes scanned grade C with 2 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 3d 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
--header "Authorization: $(printenv LINEAR_API_KEY)" \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "https://api.linear.app/graphql" \ 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
1 file 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.
- 3d ago First seen · 508 lines · 18 tokens per session scan C 98182683fef4
release-notes is a skill published in the GitHub repository anyproto/anytype-ts (8,733 stars, last pushed yesterday), with no licence file. It adds 18 tokens to every session and 5,424 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (harvests environment variables, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
powerscroll-release
Prepare, publish, verify, or audit PowerScroll application, GitHub Pages, npm MCP, and official MCP Registry releases. Use for version bumps, tags, release workflows, deployment checks, or distribution failures; do not use for ordinary feature implementation before release preparation begins.
publish
Prepare an npm release — decide which @antseed/ packages need version bumps, apply them, validate the set, and open the bump PR. Publishing itself happens in CI.
release-new-version
Release a new desktop stable version for Anarlog. Use when asked to cut, publish, or prepare a new stable desktop release after checking and merging the changelog.
new-changelog
Create the next desktop changelog entry when asked to add a changelog file or prepare the next release note under packages/changelog/content. Use this when the task is specifically about determining the next version and creating the markdown entry.
start9-frontend
Start9 house style for every Angular + Taiga UI web frontend (StartOS ui/setup-wizard, StartWRT, StartTunnel, brochure-marketplace, start9-store, ops-server, support-server). Use BEFORE writing or reviewing any frontend code in these apps — components, templates, styles/CSS, forms, dialogs/toasts, routing, state, DI…
publish
Publish the Octop Python package: cut a release branch from develop, bump version, update CHANGELOG, open a PR to main; after merge, Actions tag on main (PyPI / Docker Hub) and sync main into develop. Use when the user asks to publish, release, bump version, cut a release, or run /publish.