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 paulirish/dotfiles --skill lexicongit clone --depth 1 https://github.com/paulirish/dotfilesWrote 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/paulirish/dotfiles/lexicon)<a href="https://agentmods.dev/skills/paulirish/dotfiles/lexicon"><img src="https://agentmods.dev/badge/skills/paulirish/dotfiles/lexicon/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/paulirish/dotfiles/lexicon"><img src="https://agentmods.dev/badge/skills/paulirish/dotfiles/lexicon.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.00067 | $0.01669 |
| Opus 5.5 | $0.00027 | $0.00668 |
| Sonnet 5.5 | $0.00013 | $0.00334 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
lexicon 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 11d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 11d ago Changed · +1 lines d772d90d295e
- 18d ago Changed · +1 lines d927ce376973
- 1mo ago First seen · 99 lines · 67 tokens per session scan A 5afd5ff4e794
lexicon is a skill published in the GitHub repository paulirish/dotfiles (4,360 stars, last pushed 12d ago), with no licence file. It adds 67 tokens to every session and 1,669 once invoked, about $0.0003 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-09-14.
Other skills, from other repositories
agent-review
Conducts independent, read-only code reviews of branches, diffs, commits, working trees, or pull requests using external CLI agents (Codex, Claude, agy) or a synthesized review workflow. Focuses strictly on actionable defects and evidence-based findings. Use when reviewing code changes, requesting a second opinion on…
code-simplifier
Refines existing code for clarity, readability, and maintainability without changing behavior, interfaces, or outputs. Use when asked to "simplify", "clean up", "refactor for readability", "reduce complexity", or polish code without adding features. Don't use when the request involves changing behavior, adding…
git-review
Review code changes, pull requests, or merge requests for bugs, code quality, security, and maintainability. Use when asked to review a PR, MR, diff, or set of changes. Also handles GitHub PRs and GitLab MRs.
address-review
Take a GitHub PR's review feedback end to end: fetch unresolved threads from bots and humans, judge each, apply fixes, push, then reply and resolve. Use for "address the review" or "go through the PR feedback".
review-axes
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
pr-status
Report mergeability and review/CI status for GitHub pull requests in a compact dashboard. Use when checking whether a PR is mergeable, blocked, or ready to merge; when asked for "PR status", "review status", "is it mergeable", "what's blocking this PR", "are my PRs ready", or to check CI/check status across one or…