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 ccoalm/ccl-skills --skill test-artifact-managementgit clone --depth 1 https://github.com/ccoalm/ccl-skillsWrote 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/ccoalm/ccl-skills/test-artifact-management)<a href="https://agentmods.dev/skills/ccoalm/ccl-skills/test-artifact-management"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-skills/test-artifact-management/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/ccoalm/ccl-skills/test-artifact-management"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-skills/test-artifact-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00129 | $0.07852 |
| Opus 5 | $0.00064 | $0.03926 |
| Sonnet 5 | $0.00026 | $0.01570 |
| Haiku 4.5 | $0.00013 | $0.00785 |
Grade A, and why
test-artifact-management 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.
How it starts
The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Artifact Management
This skill owns the workflow from source (requirements doc or code) to structured test case design to Feishu Bitable delivery. It routes test layer selection to testing-strategy and Bitable operations to references/bitable-setup.md.
Bitable ownership:
- This skill owns testcase design and testcase-table delivery: initialize or reuse the Base/table, add missing canonical fields, and create, import, update, sync, or deprecate testcase records.
- Use
lark-basefor concrete Base operations andreferences/bitable-setup.mdas the canonical schema and safe write path. An existing.feishu/project.yamlmay provide reusable identifiers, but it is optional and must not trigger creation of unrelated Wiki/Base infrastructure.
Skill Routing
- Ambiguous "写测试用例" / "write test cases" requests mean
testing-strategyfirst when the user wants test code, E2E/browser/device tests, CI coverage, mocks, or verification evidence. Use this skill only when the deliverable is a structured TC artifact, Feishu/Bitable sync, or source-to-TC generation workflow. - Use
testing-strategyto decide which test layers (unit / integration / E2E / scenario) are needed after the use cases are written. - Test-code implementation, once test cases are approved, must go to the owning stack skill:
go-microservice-dev/python-service-dev/nodejs-service-dev/web-react-dev/miniapp-product-dev/app-cross-platform-dev. - Use
product-rd-workflowwhen the test case work is part of a broader feature delivery plan. - Use
llm-inference-integrationwhen test cases cover LLM / agent / RAG / inference behavior. - Use
skill-extraction-workflowto feed lessons from test case generation or Feishu Bitable setup back into this skill after each delivery cycle.
Scope: one config per deployable unit
A deployable unit is anything that ships with its own release cadence and owner: a web frontend, a mini-program, an app, an admin/运营后台 frontend, one backend service. TC management is scoped per unit — not per repo.
What ships with it
23 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.
- agents/openai.yaml 244 B
- references/.gitignore 13 B
- references/AGENTS.md 672 B
- references/bitable-setup.md 25 KB
- references/ci_templates/github-actions.yml 4.4 KB
- references/ci_templates/gitlab-ci.yml 2.4 KB
- references/ci_templates/jenkins.Jenkinsfile 3.4 KB
- references/ci_templates/README.md 4.9 KB
- references/classical-test-design-techniques.md 14 KB
- references/gen_report.py 119 KB runs code
- references/makefile-template.md 9.9 KB
- references/report-config-schema.md 13 KB
- references/run_pytestless.py 16 KB runs code
- references/source-to-case-workflows.md 14 KB
- references/tc_helpers/AGENTS.md 602 B
- references/tc_helpers/tc.dart 3.8 KB
- references/tc_helpers/tc.go 6.3 KB
- references/tc_helpers/tc.py 4.5 KB runs code
- references/tc_helpers/tc.ts 11 KB runs code
- references/tc-marker-conventions.md 11 KB
- references/tc-review-and-prioritization.md 7.8 KB
- references/test_gen_report.py 82 KB runs code
- references/update-lifecycle.md 6.6 KB
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 Changed 9d40a4f2bb66
- 11d ago First seen · 409 lines · 129 tokens per session scan A 7a814183111d
test-artifact-management is a skill published in the GitHub repository ccoalm/ccl-skills (6 stars, last pushed today), licensed Apache-2.0. It adds 129 tokens to every session and 7,852 once invoked, about $0.0006 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-31.
Other skills, from other repositories
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.