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 beyondwin/FixThis --skill fixthis-release-smokegit clone --depth 1 https://github.com/beyondwin/FixThisWrote 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/beyondwin/fixthis/fixthis-release-smoke)<a href="https://agentmods.dev/skills/beyondwin/fixthis/fixthis-release-smoke"><img src="https://agentmods.dev/badge/skills/beyondwin/fixthis/fixthis-release-smoke/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/beyondwin/fixthis/fixthis-release-smoke"><img src="https://agentmods.dev/badge/skills/beyondwin/fixthis/fixthis-release-smoke.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.00016 | $0.00221 |
| Opus 5.5 | $0.00006 | $0.00088 |
| Sonnet 5.5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
fixthis-release-smoke 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.
What it actually says
FixThis Release Smoke
Use only from a FixThis source checkout when a maintainer asks to validate release readiness or public release reality.
Rules:
- FixThis remains debug-only and Jetpack Compose-only.
- Do not commit
.fixthis/. - Separate repository checks, connected Android proof, and live registry reality.
- DEFERRED and SKIPPED are not PASS.
- Do not tag, publish, push, or edit a downstream repository unless explicitly requested.
- Use docs/contributing/release-readiness.md as the maintained release contract.
Workflow:
- Run npm run release:reality and record live/public evidence separately.
- Run npm run evidence:release for the repository evidence profile.
- Run npm run android:proof -- --strict --continue when connected proof is required.
- Run npm run release:check before a release PR or tag.
- Report PASS, FAIL, DEFERRED, and SKIPPED separately with reasons and residual risk.
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 First seen · 24 lines · 16 tokens per session scan A c61538eb0848
fixthis-release-smoke is a skill published in the GitHub repository beyondwin/FixThis (5 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 221 once invoked, about $0.0001 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
release-kotlin-library
Use when preparing, publishing, or checking readiness for a Kotlin library release, including verifying its gradle-maven-publish-plugin prerequisite, reconciling changelogs and API snapshots, and checking publication.
findeck-release
A document-review workflow that works on one specification document and only the higher-level or reference documents configured for it. It supports reference and revise actions and records history with reference-specific snapshots.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
validate-release-green
Run or inspect the local Release-Green observer for an exact base or combined PR candidate, separating hard failures, advisory drift and incomplete evidence. Use for maintainer preflight; full CI acceptance remains a separate requirement.
compose-ui-testing-patterns
Use when writing or reviewing Jetpack Compose UI tests, screenshot tests or baseline-recording evidence, previews, semantics assertions, fake image loading, keyboard input, focus assertions, interaction state (hover/pressed/focused), or tests for plain state-driven UI composables.
verify-and-ship
Choose proportionate validation, fix failures, update the changelog, commit, push, and create/update the pull request or merge request.