Borrowing it
Nothing to install: this file belongs to XAIHT/Tlamatini. 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/XAIHT/Tlamatini/main/.codex/skills/tlamatini-release-validation/SKILL.mdgit clone --depth 1 https://github.com/XAIHT/TlamatiniWrote 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/xaiht/tlamatini/tlamatini-release-validation)<a href="https://agentmods.dev/skills/xaiht/tlamatini/tlamatini-release-validation"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/tlamatini-release-validation/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/xaiht/tlamatini/tlamatini-release-validation"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/tlamatini-release-validation.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.00046 | $0.01385 |
| Opus 5.5 | $0.00018 | $0.00554 |
| Sonnet 5.5 | $0.00009 | $0.00277 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade A, and why
tlamatini-release-validation 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 today.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tlamatini release validation
Current release: v1.90.0. Dated records below retain their original evidence dates.
Test the deliverable the user will run. A source test, registry helper test, mock installer, or package inspection cannot substitute for the compiled Installer.exe completing against its actual pkg.zip.
Scope and authority
Read the checkout's AGENTS.md, CLAUDE.md and TestsVisiblesAndVisibleExecutionFromClaude2Codex.md. Preserve unrelated edits and the user's commit prohibition. Do not run build.py merely to test: it deletes the development database and dist directory. Do not edit protected database backup/restore mechanics. Use the existing release when available.
Read the acceptance matrix for a full run. For a focused regression, identify the relevant cases and label the result as focused. Never call a partial run a complete release pass.
Establish a real clean baseline
- Identify the exact release folder, Installer.exe, pkg.zip, Uninstaller.exe, installation directory and user-owned state. Record versions and hashes.
- A clean-install request authorizes removing the specified installation and its Tlamatini-owned registrations. A generic test request alone does not authorize deleting an existing personal installation; use a disposable Windows account/machine or obtain the missing authorization.
- For an authorized reset, inspect the preview from scripts/tlamatini_clean_install.ps1 before using -Execute. Its installation path must be explicit, distinct from the checkout, and free of reparse points. It exports application-owned registry keys before removal. Leave other applications and Windows-managed UserChoice values untouched.
- Verify the directory is absent, the Tlamatini desktop shortcut is absent, application ProgIDs/capabilities/Installed Apps/discovery are absent, and no installed process or service port remains. Record any Windows-managed residue. Reinstalling over the failed installation is not a clean-install test.
What ships with it
2 files 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.
- today Changed 8159b9283abd
- 2d ago Changed 0a55a289ddcc
- 3d ago Changed f9c7d60ff8d2
- 6d ago Changed · +3 lines c4a77254d874
- 19d ago First seen · 118 lines · 46 tokens per session scan A b4cacc3f691b
tlamatini-release-validation is a skill published in the GitHub repository XAIHT/Tlamatini (15 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,385 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-10-05.
Other skills, from other repositories
review
Review current code changes for bugs, regressions, test gaps, and project-guideline violations.
engineering-workflow
A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.
writing-tests
Kiro Crew repo only: how to write a backend pytest test with NO side effects that does not flake. Use when adding, editing, reviewing or debugging a test there: which conftest applies, what leaks (temp dirs, data home, /.kiro, cron, threads), the seven flake classes, cross-platform traps.
pod-e2e
ONLY for developing Kiro Crew itself -- if the project you are working on is anything else, ignore this skill: it drives Kiro Crew's own pod tooling, which does not exist in another repository. Boots a Kiro Crew feature worktree's full stack as an ISOLATED throwaway pod and proves it boots, authenticates and renders…
dashboard-template
Kiro Crew repo only: load this when a task will author or change a dashboard page. A page never ships alone: the same PR carries its TypedDict contract, its provider, and a parity test that the two agree. Scaffold all four from one field list; read numbers from an existing fold, never type them.