Borrowing it
Nothing to install: this file belongs to cp-yu/cc-switch-web. 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/cp-yu/cc-switch-web/main/.pi/skills/xirang-apply-change/SKILL.mdgit clone --depth 1 https://github.com/cp-yu/cc-switch-webWrote 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/cp-yu/cc-switch-web/xirang-apply-change)<a href="https://agentmods.dev/skills/cp-yu/cc-switch-web/xirang-apply-change"><img src="https://agentmods.dev/badge/skills/cp-yu/cc-switch-web/xirang-apply-change/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/cp-yu/cc-switch-web/xirang-apply-change"><img src="https://agentmods.dev/badge/skills/cp-yu/cc-switch-web/xirang-apply-change.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.00033 | $0.00908 |
| Opus 5.5 | $0.00013 | $0.00363 |
| Sonnet 5.5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
xirang-apply-change 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 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.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement tasks from an Xirang change.
Xirang Philosophy
- Xirang is a structured representation of human intent that an Agent can compile.
- One Xirang Semantic Model is persisted as a single whole in the four partitions
metamodel/,elements/,relationships/, andviews/; a Semantic Delta uses the same four partitions and addsoperation. - A change reconciles a Semantic Delta toward the target steady state.
proposal.md,design.md, andtasks.mdare compilation scaffolding, not competing sources of truth. - The Xirang Semantic Model is complete only when an Agent need not guess decisions that affect element hierarchy, contracts, or relationships.
- The Agent acts like a compiler and faithfully translates authorized human intent. Existing code is current implementation evidence and MUST NOT silently override the Xirang Semantic Model.
For workflow-managed writes, read the resolved file definition before its instruction and template, and MUST NOT copy definitions, config projections, or reasoning into artifacts.
Flow Outline
- Step 1: Preparation — read
.xirang/references/xirang-apply-step-1-preparation.md. - Step 2: Pre-flight scan — read
.xirang/references/xirang-apply-step-2-preflight-scan.md. - Step 3: Isolation router — read the one method reference selected by Step 1; do not load mutually exclusive methods.
- Phase 0 implementation — Master executes pending tasks serially with the implementation discipline below.
- Step 4: Phase 1 verification — read
.xirang/references/xirang-apply-step-4-phase1-verification.mdand delegate to the clean-contextxirang-revieweragent. - Step 5: Phase 2 optimization — read
.xirang/references/xirang-apply-step-5-phase2-optimization.mdand delegate to the clean-contextxirang-optimizeragent when eligible. - Step 6: Phase 3 seal — read
.xirang/references/xirang-apply-step-6-phase3-seal.md. - Step 7: Output — read
.xirang/references/xirang-apply-step-7-output.md.
Implementation Discipline
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 · 48 lines · 33 tokens per session scan A 0f9f4dac4c16
xirang-apply-change is a skill published in the GitHub repository cp-yu/cc-switch-web (47 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 908 once invoked, about $0.0001 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-12.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.