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/echovic/blade-code/engineering-quality-and-deliverynpx skills add echoVic/blade-code --skill engineering-quality-and-deliverygit clone --depth 1 https://github.com/echoVic/blade-codeWrote 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/echovic/blade-code/engineering-quality-and-delivery)<a href="https://agentmods.dev/skills/echovic/blade-code/engineering-quality-and-delivery"><img src="https://agentmods.dev/badge/skills/echovic/blade-code/engineering-quality-and-delivery.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.00132 | $0.02327 |
| Opus 5 | $0.00066 | $0.01163 |
| Sonnet 5 | $0.00026 | $0.00465 |
| Haiku 4.5 | $0.00013 | $0.00233 |
Grade A, and why
knowledge-engineering-quality-and-delivery 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 2d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module Structure
该域不是单一模块，而是把确定性测试、付费模型轨迹、制品级门禁和 tag 驱动发布串成一条跨 CLI、Web、ACP、TUI 与文档的交付链。
Directory Layout
packages/cli/tests/— CLI 核心的 unit、integration、CLI、E2E、real-api、performance、snapshot 与 security 测试packages/cli/web/tests/— Web 组件、Store、服务和 bundle 预算测试packages/cli/scripts/— 测试运行器、资格编排、构建、凭据加载与发布脚本scripts/— 仓库级发布辅助和独立基准脚本.github/workflows/— CI、tag 发布与 Docs Pages 部署docs/— 中文默认站点、英文镜像、设计规格和准出证据package.json、packages/cli/package.json— 工作区命令、发布包边界与版本biome.json、packages/cli/vitest.config.ts、packages/cli/web/vitest.config.ts— 静态检查与测试项目定义
Key Entry Points
createQualificationPlan()inpackages/cli/scripts/qualification.ts— 定义本地 14 项和生产 16 项顺序门禁testTypesinpackages/cli/scripts/test-config.js— 定义各 Vitest 项目、超时、环境和发布阻断文件白名单packages/cli/scripts/build.ts— 构建 CLI ESM 产物并把 Web 输出到同一发布目录.github/workflows/ci.yml— 聚合确定性 CI 作业.github/workflows/publish.yml— 校验 tag/包版本并通过 npm Trusted Publishing 发布.github/workflows/docs.yml— 生成文档站 changelog 并部署 Pages
Branching Table
| 维度 | 本地或确定性分支 | 生产或发布分支 |
|---|---|---|
| 资格入口 | qualify:local 顺序执行 14 项且不接触付费凭据 |
qualify:production 在本地门禁后追加 Chromium preflight 和付费真实 API |
| 测试证据 | unit/integration/E2E 允许隔离、mock 或本地 fixture | release matrix 要求真实 Provider、production surface 和宿主侧副作用证据 |
| 覆盖率与性能 | coverage 插桩运行除 performance 外的项目 | performance 在 production build 后独立运行，避免插桩污染时序 |
| 发布准备与发布 | 本地负责冻结候选、版本、双语 changelog、资格证据与 tag | tag workflow 只校验版本、构建、幂等发布 npm/GitHub Release |
| 文档源与站点产物 | docs/、CHANGELOG.md、CHANGELOG.zh.md 是 Git 可见源 |
docs/changelog.md 与 docs/en/changelog.md 在部署时生成且被忽略 |
| 浏览器依赖 | npm 包携带固定 Playwright 运行库但不下载 Chromium | 浏览器门禁要求显式安装并通过离线 launch/close preflight |
Affected Scope
packages/cli/src/— 每个运行时变更都要映射到确定性回归与适当的真实轨迹packages/cli/web/src/— Web 行为同时受组件测试、production Chromium 轨迹和 bundle 预算约束packages/cli/tests/— 汇集本地回归、跨表面驱动、资源回收和发布矩阵packages/cli/scripts/— 决定测试项目选择、超时、凭据隔离、构建顺序和本地发布行为.github/workflows/— 把静态检查、跨平台 smoke、coverage、安全审计、npm 与 Pages 分成独立作业packages/cli/package.json— 发布版本、npm 文件清单、运行时依赖和质量命令的权威入口CHANGELOG.md、CHANGELOG.zh.md— 英文包内更新信息与中文同步发布记录docs/— 用户行为契约、设计冻结记录和可审计的资格证据
What ships with it
4 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.
- 2d ago First seen · 87 lines · 132 tokens per session scan A 07e4ef739bb2
knowledge-engineering-quality-and-delivery is a skill published in the GitHub repository echoVic/blade-code (178 stars, last pushed yesterday), licensed MIT. It adds 132 tokens to every session and 2,327 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
golang-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
audit-harness
Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.
deploy
Deploy the application or manage infrastructure. Handles Docker builds, CI/CD, and deployment workflows.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.