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/ktkid/x-dev-pipeline/x-devnpx skills add KtKID/x-dev-pipeline --skill x-devgit clone --depth 1 https://github.com/KtKID/x-dev-pipelineWhat 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.00057 | $0.00624 |
| Opus 5 | $0.00028 | $0.00312 |
| Sonnet 5 | $0.00011 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
x-dev 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.
What it actually says
x-dev — 统一执行
输入与边界
目标目录必须有 README.md 和 dev-checklist.md。README 的 risk:、验收 Scenario 与技术设计定义实现边界；dev-checklist 定义顺序与状态；dev-report 记录改动及 verify 证据。x-dev 消费 task，不创建需求包。
执行
- 阅读 README 的核心目标、涉及模块、架构拆分策略、技术设计、验收与自动化测试责任；模块段含 spec 引用时跟读对应模块文档。
- 运行
python3 tools/xdev.py status <task-dir> --json与graph <task-dir> --json。同优先级、无依赖、无同文件写冲突的 ready task 可并行；有依赖的 task 按拓扑序推进。 - 将当前 checklist 项更新为进行中，实现时保持 README 定义的公开契约、失败路径与范围。
- 每个
验证: autoScenario 在dev-report.md写一个 auto fencedverify块，用scenario:精确回指；补齐单元、契约和边界测试。manual Scenario 写步骤块。 - 实现完成后更新 checklist 为待测试，运行全部 verify 块声明的命令；通过后更新为测试通过。
- 运行
python3 tools/xdev.py verify <task-dir> --json：exit 2 修正 dev-report 格式；exit 1 将 fail 与 uncovered 一次交给 x-fix；exit 0 继续 risk 路由。 - Q0/Q1 输出完成回执及定级依据；Q2 调 x-qa-gate RC；Q3 调 x-qa-gate R1→R2→R3。Gate ② 全部通过后把 checklist 标为
[x] ✅。
状态与记录
状态顺序为 [ ] ⏳ → [ ] ▶️ → [ ] 🟡 → [x] 🟢 → [x] ✅；Gate ② 负责最终 ✅。reports/ 位于 task 根目录下，verify 或 qa-gate fail 依既有共享 fix-counter 交给 x-fix 批量修复。
完成回执
报告当前 task、完成项、修改文件、verify 结果、risk 路由、Gate ② 结果、manual 待验收项和遗留阻塞。连续模式在一个 task Gate 完成后按 graph 读取下一批 ready 项。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 31 lines · 57 tokens per session scan A dcae67798b14
x-dev is a skill published in the GitHub repository KtKID/x-dev-pipeline (12 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 624 once invoked, about $0.0003 per session on Opus 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-08-30.
Other skills, from other repositories
multi-agent-skill-sharing
Install a skill once and make it usable across multiple AI coding agents (Claude Code, Codex CLI, Cursor, Gemini CLI, Cline, etc.) that work on the same repository. Use this when the user wants a skill / ruleset / prompt to be shared and switchable across several AI products, asks "why can only one tool use this…
implement
Use in the Implement phase whenever writing or editing production Java code, or fixing a bug, in a Spring/Spring Boot project. Enforces test-first (red-green-refactor), executes the approved plan step by step, and honors the project's path-scoped tech-stack rules and the task's enforcement set. Preloaded into…
review
Use in the Review phase before claiming any Java/Spring task is complete, fixed, or passing. Spawns the auditor subagents that check the implementation against every applicable skill, rule, and memory item, runs the test suite for fresh evidence, and re-spawns for at most two fix rounds before reporting what survives.…
claudehut-workflow
Use at the start of every session and whenever beginning a coding task in a Java/Spring backend - establishes the ClaudeHut 7-phase agentic workflow, the complexity-tier routing that lets small tasks skip deliberation phases, and the laws that govern which skills and rules must fire. Injected at session start; also…
brainstorm
Use to generate and weigh solution approaches for a problem, after discovery has grounded the context. Produces two or more genuinely distinct options scored on trade-offs, recommends one, and (for code tasks) assembles the enforcement set the rest of the workflow audits against. General-purpose ideation — works for…
discover
Use as the FIRST phase of EVERY coding task, before brainstorming - grounds the work in the existing codebase (entry points, key types, structure) and proves whether something reusable already exists. Produces the reuse-scan artifact the write gate requires and the reuse DECISION (adopt / extend / new). Runs inline on…