Borrowing it
Nothing to install: this file belongs to layer1labs/specsmith. 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/layer1labs/specsmith/main/.agents/skills/testing-cicd-integration/SKILL.mdgit clone --depth 1 https://github.com/layer1labs/specsmithWrote 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/layer1labs/specsmith/testing-cicd-integration)<a href="https://agentmods.dev/skills/layer1labs/specsmith/testing-cicd-integration"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/testing-cicd-integration/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/layer1labs/specsmith/testing-cicd-integration"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/testing-cicd-integration.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.00020 | $0.00405 |
| Opus 5.5 | $0.00008 | $0.00162 |
| Sonnet 5.5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
testing-cicd-integration 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 2mo 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
Testing Integration with CI/CD
This skill enables specsmith projects to integrate testing frameworks with CI/CD pipelines while maintaining governance compliance.
Requirements Covered
- REQ-106: Testing Integration with CI/CD
- Allows specsmith projects to integrate testing frameworks with CI/CD pipelines with human approval
Integration Capabilities
CI/CD Features
- Pipeline integration for automated testing
- Test execution in CI environments
- Integration with popular CI platforms (GitHub Actions, GitLab CI, Jenkins)
- Test result reporting to CI systems
- Parallel test execution in CI environments
- Environment variable management for tests
Governance Requirements
- Human approval required for CI/CD integration
- Configuration management with governance controls
- Approval-based pipeline setup
- Audit logging of CI/CD activities
Usage Examples
# Initialize CI/CD integration
specsmith skill install testing-cicd-integration
# Configure CI/CD settings
specsmith test cicd configure --platform github-actions --test-parallel true
# Set up CI pipeline
specsmith test cicd setup --pipeline e2e-tests --trigger on-push
Configuration
The skill requires the following configuration in scaffold.yml:
cicd:
platform: github-actions
test_parallel: true
test_timeout: 30000
trigger_on: "on-push"
report_results: true
artifact_storage: "github-artifacts"
Security Considerations
- All CI/CD integrations require human approval
- Pipeline secrets must be properly secured
- Test environment access must be controlled
- Integration with CI systems must be secure
Compliance Requirements
- Follow security best practices for CI/CD integrations
- Maintain audit logs of all CI/CD activities
- Ensure proper pipeline configuration and management
- Enforce approval-based CI/CD setup
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.
- 2mo ago First seen · 71 lines · 20 tokens per session scan A a58c2e4345ce
testing-cicd-integration is a skill published in the GitHub repository layer1labs/specsmith (8 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 405 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-08-31.
Other skills, from other repositories
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
staging-validation-phase
Guides manual staging validation before production deployment through smoke tests, critical user flow testing, data migration verification, and rollback capability checks. Use when validating staging deployments, running pre-production tests, or preparing for production promotion in staging-prod deployment model.…
responsive-audit
Responsive audit: test pages at 375/768/1024px breakpoints via Playwright. Checks overflow, tap targets, sidebar collapse, text reflow, WCAG 1.4.4 zoom.
test-audit
Static test-suite quality audit - coverage from lcov/Istanbul/Cobertura/go/tarpaulin reports, pyramid shape (unit/integration/e2e ratio), anti-patterns (.only leaks, skipped tests, no-assertion tests, hardcoded sleeps). Stack-aware across 11 supported stacks.
pin-guardrail
Pin a shell guardrail (a hook, a git hook, a checker script) with a behavioral test suite, prove the suite is real by mutating the code, and wire it into CI with its mutation ledger. Use when asked to "add tests for this hook", "pin that guard", "mutation-test this script", "this hook has no test", "wire the suite…
github-actions-workflows
GitHub Actions workflow patterns for CI/CD including matrix builds, reusable workflows, secrets management, and caching strategies. Use when setting up or optimizing GitHub Actions pipelines.