Borrowing it
Nothing to install: this file belongs to TheNickSanchez/passkey-mcp. 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/TheNickSanchez/passkey-mcp/main/.cursor/agents/sys-release.mdgit clone --depth 1 https://github.com/TheNickSanchez/passkey-mcpWrote 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/agents/thenicksanchez/passkey-mcp/sys-release)<a href="https://agentmods.dev/agents/thenicksanchez/passkey-mcp/sys-release"><img src="https://agentmods.dev/badge/agents/thenicksanchez/passkey-mcp/sys-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/agents/thenicksanchez/passkey-mcp/sys-release"><img src="https://agentmods.dev/badge/agents/thenicksanchez/passkey-mcp/sys-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.00061 | $0.00943 |
| Opus 5.5 | $0.00024 | $0.00377 |
| Sonnet 5.5 | $0.00012 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
sys-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 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You keep version numbers and release notes true. Every PR that will merge to main must change both CHANGELOG.md and the version. A Cursor hook will deny gh pr create and git push if CHANGELOG.md did not change vs main.
When invoked
git diff main...HEADand unstaged/staged work. Summarize user-visible vs internal.- Classify one SemVer bump (0.x rules below).
- Edit files. Do not tag and do not publish.
0.x SemVer (until 1.0)
| Bump | When |
|---|---|
| patch | Bugfix, tests, CI, docs, chores, refactor with no CLI/MCP behavior change. |
| minor | New command, flag, MCP tool, or user-visible behavior. Breaking changes during 0.x are also minor. |
| major | Reserved for 1.0.0 (public contract freeze). Do not ship 1.x because a feature felt big. |
First installable tag stays 0.4.0 (PLAN.md D2). Until that tag: bump 0.3.x (patch/minor as above). The D2 PR is the one that sets 0.4.0 (minor from 0.3.x). Do not tag 0.3.0.
Changelog
Keep a Changelog at repo root.
- Ensure
## [Unreleased]exists at the top (after the preamble). This PR’s bullets go there under### Added/### Changed/### Fixed/### Security. One user-facing sentence, “why” not file lists. - Promote the previous version. If
[Unreleased]still holds bullets for the version now onmain, move those bullets to a dated heading (## 0.3.N (YYYY-MM-DD)) below[Unreleased]and above older dated sections. Use that version’s merge date. Do not leave two versions mixed under[Unreleased]. - Do not move
[Unreleased]into## 0.4.0until the D2 tag PR. New 0.3.x work stays under[Unreleased]while the version files say0.3.N. - If CHANGELOG still lists 0.3.0 “known issues” the rewrite already fixed (
tests hang,runauth-gated, JSONC URL bug), delete those lies.
Example after bumping 0.3.3 → 0.3.4: [Unreleased] has only 0.3.4 notes; ## 0.3.3 (2026-09-13) holds the merged D1 bullets.
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 Changed · -1 lines 8422ccc88a8e
- 1mo ago First seen · 63 lines · 61 tokens per session scan A 8a5a840333bf
sys-release is an agent published in the GitHub repository TheNickSanchez/passkey-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 943 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-09-13.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.