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 KtKID/x-dev-pipeline --skill x-verifygit clone --depth 1 https://github.com/KtKID/x-dev-pipelineWrote 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/ktkid/x-dev-pipeline/x-verify)<a href="https://agentmods.dev/skills/ktkid/x-dev-pipeline/x-verify"><img src="https://agentmods.dev/badge/skills/ktkid/x-dev-pipeline/x-verify.svg" alt="Measured on agentmods" 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.00055 | $0.00366 |
| Opus 5 | $0.00028 | $0.00183 |
| Sonnet 5 | $0.00011 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
x-verify 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 7d 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-verify · Gate ①
输入
README.md 的验收 Scenario 与 dev-report*.md fenced verify 块。引擎负责复跑命令、比较 exit/输出、列出 manual 和自动场景覆盖。
流程
- 运行
python3 tools/xdev.py verify <task-dir> --json。 - exit 0：输出
pass N / manual M回执，不写报告。 - exit 1：读取 fail 的
output_tail与 uncovered，必要时用--only <id>复跑一个块；写reports/verify/verify-report-<timestamp>.md，将完整 failure 清单交 x-fix。 - exit 2：指出 dev-report verify 格式或路径问题，退回 x-dev；不递增 fix-counter。
约束
- 只报告命令与覆盖事实；代码质量由 x-qa-gate 处理。
- fail 时跑完全部 auto 块后一次交付完整清单。
reports/.fix-counter、三轮上限和 x-fix 批量修复协议保持现有定义。
回执
🛡️ Gate① verify ✅ · pass N · manual M 待人工
🛡️ Gate① verify ❌ · fail N · uncovered M → x-fix
What ships with it
1 file 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.
- 7d ago First seen · 33 lines · 55 tokens per session scan A 868a5b2eae3e
x-verify is a skill published in the GitHub repository KtKID/x-dev-pipeline (12 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 366 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
maintainer-preflight
Use before claiming work is done, before committing, and before opening a PR in this repo — runs the mcp-server test/typecheck/build gates and the committed-bundle rule. Trigger on "done", "ready to commit", "open a PR", or any completion claim.
app-user-story-qa
End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.
elegant-architecture
Guides clean architecture design with strict 200-line file limits. Use when starting new features, refactoring large files, or planning module structure. Enforces modular design and real testing.
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.
skill-lifeguard
Use when a skill is brittle, drifting, repeatedly failing, or needs a Reliable Skill Contract. Trigger for phrases like skill lifeguard, reliable skill, self-maintaining skill, negative examples, verification checkpoints, drift signals, replay hooks, or failure log to skill patch. Audits or patches skills so…
test-driven-development
Enforces TDD discipline with RED-GREEN-REFACTOR cycle. Use when writing new features, fixing bugs, or refactoring code. Ensures tests genuinely verify behavior.