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 lexq-io/lexq-cli --skill lexq-recipesgit clone --depth 1 https://github.com/lexq-io/lexq-cliWrote 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/lexq-io/lexq-cli/lexq-recipes)<a href="https://agentmods.dev/skills/lexq-io/lexq-cli/lexq-recipes"><img src="https://agentmods.dev/badge/skills/lexq-io/lexq-cli/lexq-recipes/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/lexq-io/lexq-cli/lexq-recipes"><img src="https://agentmods.dev/badge/skills/lexq-io/lexq-cli/lexq-recipes.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.00000 | $0.04687 |
| Opus 5.5 | $0.00000 | $0.01875 |
| Sonnet 5.5 | $0.00000 | $0.00937 |
| Haiku 4.5 | $0.00000 | $0.00469 |
Grade A, and why
lexq-recipes 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 3d 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LexQ CLI — Recipes
Prerequisite: Read
lexq-shared/SKILL.mdfirst. Each recipe is a complete, copy-paste workflow.
Recipe 1: Tiered Discount Policy
Goal: Apply different discounts based on payment amount.
# 1. Create group
lexq groups create --json '{
"name": "tiered-discount",
"description": "Apply discount based on payment amount tiers"
}'
# → Save the group ID
# 2. Create DRAFT version
lexq versions create --group-id <gid> --json '{"commitMessage": "Initial tiered discount"}'
# → Save the version ID
# 3. Register facts (skip if already exist)
lexq facts create --key paymentAmount --name "Payment Amount" --type NUMBER --required
lexq facts create --key customerTier --name "Customer Tier" --type STRING \
--allowed-values "VIP, GOLD, SILVER"
# A value domain says which values the fact accepts. It refuses a rule literal that could
# never match (a typo like "PLATNUM"), and the Console offers a dropdown instead of a text box.
# Leave it off when the set is open — a country code, an account id, a free-text label.
# 4. Add rules — creation order becomes priority order (first created = priority 1 = highest)
lexq rules create --group-id <gid> --version-id <vid> --json '{
"name": "Premium Tier - 20%",
"condition": {
"type": "SINGLE",
"field": "paymentAmount",
"operator": "GREATER_THAN_OR_EQUAL",
"value": 500000,
"valueType": "NUMBER"
},
"actions": [{
"type": "MUTATE_FACT",
"parameters": {
"targetVar": "paymentAmount",
"method": "PERCENTAGE",
"operator": "SUB",
"operand": 20,
"rounding": { "mode": "HALF_UP", "scale": 0 }
}
}]
}'
lexq rules create --group-id <gid> --version-id <vid> --json '{
"name": "Gold Tier - 10%",
"condition": {
"type": "GROUP",
"operator": "AND",
"children": [
{ "type": "SINGLE", "field": "paymentAmount", "operator": "GREATER_THAN_OR_EQUAL", "value": 100000, "valueType": "NUMBER" },
{ "type": "SINGLE", "field": "paymentAmount", "operator": "LESS_THAN", "value": 500000, "valueType": "NUMBER" }
]
},
"actions": [{
"type": "MUTATE_FACT",
"parameters": {
"targetVar": "paymentAmount",
"method": "PERCENTAGE",
"operator": "SUB",
"operand": 10,
"rounding": { "mode": "HALF_UP", "scale": 0 }
}
}]
}'
lexq rules create --group-id <gid> --version-id <vid> --json '{
"name": "Base Tier - 5%",
"condition": {
"type": "SINGLE",
"field": "paymentAmount",
"operator": "GREATER_THAN_OR_EQUAL",
"value": 30000,
"valueType": "NUMBER"
},
"actions": [{
"type": "MUTATE_FACT",
"parameters": {
"targetVar": "paymentAmount",
"method": "PERCENTAGE",
"operator": "SUB",
"operand": 5,
"rounding": { "mode": "HALF_UP", "scale": 0 }
}
}]
}'
# 5. Validate
lexq analytics dry-run --version-id <vid> --debug --json '{"facts":{"paymentAmount":600000}}'
# Expected: mutatedFacts.paymentAmount = 480000, generatedVariables.paymentAmount__delta = -120000
lexq analytics dry-run --version-id <vid> --debug --json '{"facts":{"paymentAmount":200000}}'
# Expected: mutatedFacts.paymentAmount = 180000, generatedVariables.paymentAmount__delta = -20000
# 6. Deploy
lexq deploy publish --group-id <gid> --version-id <vid> --memo "Tiered discount v1"
lexq deploy live --group-id <gid> --version-id <vid> --memo "Go live"
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.
- 3d ago Changed · +7 lines c11724830049
- 20d ago Changed · +2 lines 48b24c4b1af1
- 27d ago Changed · +4 lines e759861ce016
- 1mo ago Changed · +4 lines e78cf2111024
- 1mo ago First seen · 479 lines · 0 tokens per session scan A c1e54b5d2b65
lexq-recipes is a skill published in the GitHub repository lexq-io/lexq-cli (0 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,687 tokens. 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
shopping
Skill "shopping" from Hmbown/Codewhale, covering shopping, when to use, setup, workflow and non-goals.
daiso-cli
A command-line interface for searching Daiso and related Korean shopping, store, food, cinema, and convenience-store data through the Daiso project. It can return structured JSON for searches and comparisons.
goofish-publish-item
A workflow for publishing second-hand items on Xianyu, a Chinese marketplace for used goods. It turns an item description and images into a category, title, listing text, and a ready-to-submit listing.
goofish-reply-buyer
A Chinese-language workflow for handling buyer messages on Xianyu, a Chinese second-hand marketplace. It reviews conversations, classifies buyer intent, and drafts replies according to the seller’s rules, but waits for human approval before sending.
goofish-shop-diagnosis
A read-only diagnostic workflow for Xianyu shops and listings. It compares how a shop’s items appear in marketplace search with their stored details to investigate visibility and sales problems.
booking-cli
Searches Booking.com from the terminal via cli-web-booking — find hotels, apartments, and hostels by destination, dates, and guests; get property details by slug; resolve destination names to IDs. Use when the user asks about Booking.com, hotel search, accommodation prices, property ratings, or comparing places to…