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/mahmoud/lithoxyl/releasenpx skills add mahmoud/lithoxyl --skill releasegit clone --depth 1 https://github.com/mahmoud/lithoxylWrote 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/mahmoud/lithoxyl/release)<a href="https://agentmods.dev/skills/mahmoud/lithoxyl/release"><img src="https://agentmods.dev/badge/skills/mahmoud/lithoxyl/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 | $0.00003 | $0.01531 |
| Opus 5 | $0.00002 | $0.00766 |
| Sonnet 5 | $0.00001 | $0.00306 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade C, and why
release scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
deactivate && rm -rf /tmp/lithoxyl-verify How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release lithoxyl
lithoxyl uses CalVer: YY.MINOR.MICRO (e.g. 26.0.1). The version lives in
lithoxyl/__init__.py as a __version__ literal string. During development it
carries a dev suffix (e.g. 26.0.1dev). Flit reads this at build time.
Tags are bare CalVer (e.g. 26.0.1, NOT v26.0.1). The publish workflow
triggers on tags matching [0-9]*.[0-9]*.[0-9]*.
Pre-flight checks
Before starting, verify ALL of these:
- Working tree is clean (
git statusshows nothing dirty/staged) - You are on
masterbranch lithoxyl/__init__.pyhas adevsuffix on__version__- All tests pass:
tox -p auto(or at minimumpytest lithoxyl/tests/ -v) - Check what is actually published on PyPI: https://pypi.org/project/lithoxyl/ PyPI is canonical. If the intended version already exists on PyPI, it cannot be re-released -- bump to the next version instead. If a local/GitHub tag exists for a version that is NOT on PyPI, the prior release failed and should be retried (see "Failed release" under Error recovery).
If any check fails, stop and report. Do not proceed with a dirty tree or failing tests.
Release steps
1. Determine the release version
Read __version__ from lithoxyl/__init__.py. Strip the dev suffix.
Example: 26.0.1dev becomes 26.0.1.
Ask the user to confirm the version. If they want a different version (e.g. bumping minor instead of micro), use that instead.
2. Update version for release
Edit lithoxyl/__init__.py: remove the dev suffix from __version__.
# Before
__version__ = '26.0.1dev'
# After
__version__ = '26.0.1'
3. Update CHANGELOG.md
Add a new section at the top of CHANGELOG.md (below the # lithoxyl Changelog
heading) for the release version. Use this format:
## 26.0.1
_(Month Day, Year)_
- First change description
- Second change description
To determine what changed, review the commits since the last tag:
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:'%s' --no-merges
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.
- 5d ago First seen · 169 lines · 0 tokens per session scan C 592d898c5390
release is a skill published in the GitHub repository mahmoud/lithoxyl (146 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 3 tokens to every session and 1,531 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gh-pull-request
Create a GitHub pull request for SkyWalking BanyanDB. Use when the user asks to create a PR, submit changes, or open a pull request.
rsyslog_changelog
Maintain rsyslog ChangeLog entries by selecting important user-visible changes, matching the release-note style, and avoiding low-signal commit-log duplication.
rsyslog_v8stable_patch_flow
Handle rsyslog post-.0 v8-stable updates, including patch-release ChangeLog sections, PRs targeting v8-stable, preserving stable merge commit hashes, and merging v8-stable back into main cleanly.
version-management
Guide to managing and promoting theme versions in WP Rig.
goshipit
Pre-launch codebase audit skill. Use this whenever someone is about to ship, deploy, launch, push to main/prod, or merge a release - even without "goshipit" explicitly. Trigger on: "is my app ready?", "can I deploy now?", "pre-deploy check", "review before launch", "is this production-ready?", "check my codebase"…
monitoring
Flutter 모니터링 & 분석 가이드라인. Firebase Crashlytics, Analytics, Performance Monitoring, Sentry 통합, 구조화된 로깅.