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 fainaltn/findeck --skill findeck-releasegit clone --depth 1 https://github.com/fainaltn/findeckWrote 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/fainaltn/findeck/findeck-release)<a href="https://agentmods.dev/skills/fainaltn/findeck/findeck-release"><img src="https://agentmods.dev/badge/skills/fainaltn/findeck/findeck-release.svg" alt="Measured on agentmods" 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.00071 | $0.00718 |
| Opus 5 | $0.00036 | $0.00359 |
| Sonnet 5 | $0.00014 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
findeck-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 7d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
findeck Release
Use this skill when the user wants to run the project-specific release flow for findeck.
What This Skill Does
This skill turns the current findeck workspace into a repeatable GitHub release path:
- Read and verify the project version
- Run release validation for web and Android
- Commit release changes on
main - Push
mainto GitHub - Build the Android debug APK release artifact
- Create the matching GitHub release from the local release notes file and attach the APK
Default Version Sources
The release version should already be updated before running the final release step.
Primary version locations:
- root package:
package.json - workspace packages:
apps/web/package.json,apps/server/package.json,packages/shared/package.json,packages/sdk/package.json - Android app:
apps/android/app/build.gradle.kts
Release notes file:
docs/release-notes-v<version>.md
Default Release Validation
Run these checks before publishing:
npm run typecheck --workspace @findeck/web
npm run build --workspace @findeck/web
cd apps/android && ./gradlew :app:compileDebugKotlin
Preferred Command
Run:
./skills/findeck-release/scripts/release_findeck.sh
This command:
- validates versions are aligned
- runs release checks
- builds the Android debug APK asset
- stages release changes
- commits
Release v<version> - pushes
main - pushes the matching git tag
- creates GitHub release
v<version> - uploads the APK asset to that GitHub release
Useful overrides:
./skills/findeck-release/scripts/release_findeck.sh --dry-run
./skills/findeck-release/scripts/release_findeck.sh --skip-release
./skills/findeck-release/scripts/release_findeck.sh --skip-apk
./skills/findeck-release/scripts/release_findeck.sh --notes-file docs/release-notes-v0.1.4.md
Guardrails
- This flow is for findeck only; the release commit title must be
Release v<version> - The Git branch must be
mainunless the user explicitly asks for something else - The release notes file must exist before release creation
- The script must fail fast on version mismatches between root, workspace packages, and Android
- The script should support
--dry-runfor safe preview - GitHub release creation should attach the prepared APK asset by default
- SMB publication stays in
apk-smb-sync; GitHub release attachment belongs here
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.
- 7d ago First seen · 90 lines · 71 tokens per session scan A a5740191a9f0
findeck-release is a skill published in the GitHub repository fainaltn/findeck (1 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 718 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-31.
Other skills, from other repositories
shepherd
Use when asked to shepherd, babysit, monitor, or poll open pull requests or merge requests, including triaging review feedback, CI failures, and routine follow-up.
github
Search repositories, view issues, check PRs on GitHub. Use when: user asks about GitHub repos, issues, PRs, or wants to search GitHub. Don't use when: user wants general web search (use research skill) or asks about git concepts without GitHub context.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
github-actions-multiplatform-release
Structure a GitHub Actions release pipeline for a multiplatform desktop app so one Linux runner cross-builds every platform's artifacts and a second, tiny macOS job does only the one step that genuinely requires macOS — with artifact handoff between them and no compilation on the costly runner; reach for it when your…
fixthis-release-smoke
Run FixThis release and trust-loop smoke checks.
android-release-bump
Bump Android release versions in app/build.gradle.kts, generate localized Play release notes, run verification, optionally run headless emulator smoke validation, commit/tag/push, build a signed AAB, and optionally upload to Google Play Internal Testing. Use when asked to cut a release, bump major/minor/patch (or…