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 spideynolove/claude-dotfiles --skill xiagit clone --depth 1 https://github.com/spideynolove/claude-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/spideynolove/claude-dotfiles/xia)<a href="https://agentmods.dev/skills/spideynolove/claude-dotfiles/xia"><img src="https://agentmods.dev/badge/skills/spideynolove/claude-dotfiles/xia/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/spideynolove/claude-dotfiles/xia"><img src="https://agentmods.dev/badge/skills/spideynolove/claude-dotfiles/xia.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.00035 | $0.01879 |
| Opus 5.5 | $0.00014 | $0.00752 |
| Sonnet 5.5 | $0.00007 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade B, and why
xia scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/xia/XIALOGUE.md 2>/dev/null || echo "XIALOGUE_MISSING" How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/xia — Borrow and Adapt from GitHub Projects
Xỉa (Vietnamese): borrow/take something from others and use it in your own product.
This is a protocol, not a workflow description. Follow each phase exactly. Output templates are mandatory — fill them in, do not paraphrase or reformat them.
CONSTRAINTS — Read before writing any code
Step 1: Read the project coding rules.
Read(file_path: "~/.claude/CLAUDE.md")
Extract and list every coding constraint found. These apply to ALL code written in this session.
Step 2: Confirm constraints before proceeding.
Output this block exactly:
## Constraints active for this session
- [list each rule from CLAUDE.md, one per line]
Do not skip this. Do not proceed to Phase 0 until this block is printed.
Usage
/xia <github-repo> [focus]
<github-repo>: GitHub URL oruser/reposhorthand[focus]: Optional — specific aspect to focus on
Storage
Xỉa state is project-local, stored inside the repo and committed to git:
<project-root>/
└── .claude/
└── xia/
├── XIALOGUE.md
└── patterns/
└── xia-[repo-slug]-[pattern].md
Install Targets
Default: always project-local first.
| What is borrowed | Install to | Promote to ~/.claude/ when |
|---|---|---|
| Pattern / workflow | .claude/xia/patterns/ |
Never — stays project-local |
| Skill | .claude/skills/ |
After 5+ sessions of proven value, on explicit user request |
| Agent | .claude/agents/ |
After 5+ sessions of proven value, on explicit user request |
| Command | .claude/commands/ |
After 5+ sessions of proven value, on explicit user request |
Never install directly to ~/.claude/ unless the user explicitly says "install globally".
Phase 0 — Know A
Input: current working directory
Step 1 — Check prior Xỉa state:
cat .claude/xia/XIALOGUE.md 2>/dev/null || echo "XIALOGUE_MISSING"
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 · 298 lines · 35 tokens per session scan B a4259d27f86b
xia is a skill published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,879 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…